wade womersley – york based software engineer
I still like serverless, but the tradeoff is obvious when something breaks at 2 a.m. The architecture is easy to ship and harder to reason about when you need logs, context, and a fast path to the real failure.
Clients do not really need a consultant who just says clever technical things. They need someone who can reduce risk, create clarity, and help them make better decisions.
A legacy system is not dangerous just because it is old. It becomes dangerous when nobody can change it safely, nobody can see what it is doing, and the business depends on it anyway.
AI can generate code faster, but that only makes direction, judgment, and accountability more important. Senior engineers still matter because the expensive mistakes are rarely typing mistakes.
Most rewrite discussions are really a sign that the team is frustrated, not that a full rebuild is the smartest technical decision. In most cases, incremental change is the better call.
AI tooling is not going away. What a lot of people are calling a bubble looks more like denial in the face of tools that are already becoming normal developer infrastructure.
TypeScript 6.0 matters, but TypeScript 7.0 looks like the real shift. The native compiler work is the part I think most teams should actually care about.
PHP 8.5.4 is a bug-fix release, not a feature release. If you are already on PHP 8.5, you should update. If you are still on 8.4, this alone is not the reason to jump.
TypeScript 6.0 is now live, but the main story is not flashy syntax. It is the upgrade work you should do now before TypeScript 7 lands.