Insights
What we are building, and what we are learning.
34 articles on Architecture, Security, AI, Hiring, Delivery, Data, Engineering, Leadership, Built with AI, Mobile, Cloud.
- Mid-migration, you run three systems. Your pen test scope lists one. (Architecture, October 26, 2026)
A legacy migration runs old and new side by side for months, joined by proxies, sync jobs and temporary accounts. That bridge is the riskiest code you own, and last year's test scope has never heard of it. - The customer said yes. Then security sent the spreadsheet. (Security, October 22, 2026)
The deal is agreed. Then the security questionnaire arrives, and a few of its rows are engineering work in disguise. How to find them, answer them honestly and still sign before the holidays. - Pen test reports land in November. Code freezes land in December. (Security, October 20, 2026)
Most of what a penetration test costs arrives after the report: engineering time nobody reserved, on code nobody owns, before a freeze nobody moved. How to sort findings by the work they need, name owners and book the retest now. - Your coding agent builds exactly what the ticket says. That is the problem. (AI, October 19, 2026)
A coding agent can turn a vague ticket into finished, tested code in an afternoon, quietly deciding everything the ticket left out. How to surface those decisions first, and why the bottleneck moves to your side. - Four hours of overlap is the standard advice. Ask which four. (Hiring, October 18, 2026)
Europe's clocks go back on 25 October and America's on 1 November, and every team split across continents feels it. Overlap is counted in the wrong unit. How to place the hours that matter, and what to ask anyone promising your hours. - The launch is late. Will more engineers help? Usually not where you'd put them. (Delivery, October 16, 2026)
Mid-October, a January launch, and a plan that needs four more weeks than the calendar holds. When added engineers rescue a date, when they sink it, and why the decision is due this month. - AI made the code cheaper. Make sure your contract noticed. (Delivery, October 16, 2026)
Buyers want AI savings in their engineering invoices, and vendors are guessing what those savings are. How to write a contract that measures the gain within weeks, decides who keeps it, and keeps quality from paying for it. - Your dashboards disagree on revenue. Moving the data will not settle it. (Data, October 16, 2026)
Finance has one revenue figure, the product dashboard has another, and the proposed fix is a new data platform. Most of the gap lives in definitions, not storage. How to find the forks, settle them, and know when a lakehouse earns its place. - .NET 8 goes out of support on 10 November. Nothing will break that day. (Engineering, October 16, 2026)
On 10 November, .NET 8 and .NET 9 stop getting security fixes. Your applications will keep running, which is exactly why the date gets missed. How to triage what you run, and what to tell the next security review. - Your voice agent must now say it is an AI. Design what happens next. (AI, October 16, 2026)
Since 2 August, voice agents answering EU callers must say they are AI, and December's grace period does not cover it. Writing the sentence is easy. How callers react to it is the cost, and the part to design. - You pay your AI agent per resolution. Who decides what resolved means? (AI, October 11, 2026)
More AI support agents are now billed per resolution, and the vendor does the counting. How to write your own definition of resolved, check it, and put it in the contract before the first invoice. - The AI budget is due this month. Price the data under it. (Data, October 11, 2026)
Most AI lines in next year's budget pay for the model, the licence and the integration, and nothing for the data the feature reads. How to size that missing line, one use case at a time. - Your embedded engineers use AI. Decide whose account it runs on. (AI, October 8, 2026)
Outside engineers will use AI on your code whatever the contract says. Banning it can drive it out of sight. The better fix is plainer: the tools run on your accounts, under your settings, and leave when the engineer does. - It's beginning to look a lot like attack season. (Security, October 8, 2026)
Ransomware crews plan around your holidays: thin staff, frozen changes, a full inbox. Why your quietest fortnight is their busiest, and the ten weeks of work that make it boring again. - The one engineer who knows the system has resigned. Spend the notice well. (Leadership, October 8, 2026)
One person knows how the old system really runs, and they have just handed in their notice. Asking them to write it all down is the usual move and the wrong one. How to spend the weeks you have. - The CRA's 24-hour clock is live. It starts in your support inbox. (Security, October 7, 2026)
Since 11 September 2026, makers of software and connected products sold in the EU must flag exploited vulnerabilities within 24 hours. Filing is the easy part. Noticing in time is not. - Your AI feature passed the pen test. Nobody tested the AI. (Security, October 7, 2026)
The annual penetration test came back clean, and the new AI assistant was barely touched. Why conventional scopes miss AI features, how to size the risk, and what a real test should cover. - Ten questions to ask an engineering partner before you sign. (Hiring, October 6, 2026)
Every vendor says senior, agile and AI-enabled. These are the ten questions that separate them, with what a good answer sounds like and what should worry you. - Staffing or a managed team? Split the work, not the difference. (Delivery, October 6, 2026)
Most comparisons treat embedded engineers and managed delivery as one choice for the whole company. Real roadmaps hold both kinds of work. Decide per workstream, then design the seams between them. - .NET or Node? Choosing between the two stacks that run most business software. (Engineering, October 5, 2026)
The Microsoft stack and the JavaScript stack are both excellent, and both are surrounded by myths. What each is really good at, what each costs, and how to choose without starting a religious war. - Hiring embedded engineers? First, find who will steer them. (Hiring, October 5, 2026)
Embedded engineers work under your direction. That is the point, and the catch: direction costs hours. How to check you have them before day one, and what to buy instead if you do not. - Every engineering engagement ends. Plan the exit before you sign. (Delivery, October 5, 2026)
The cheapest moment to arrange a clean handover is before the first commit. What you must own, what AI-native delivery adds to the list, and how to rehearse leaving while everyone is still friendly. - We pushed AI as far as it would go. It shipped a real-time strategy game. (Built with AI, October 4, 2026)
An Unreal Engine 5.8 strategy game, a cloud backend, an AI commander that talks back, and a trailer edited by code. What was built, how, and what it proves about engineering with AI. - Meet Jev: the model that decides which model you can afford. (AI, September 22, 2026)
A new kind of AI model does not write a word. It makes decisions, in milliseconds, for almost nothing. That makes it a natural fit for one expensive problem: choosing the right LLM for every request. - AI coding agents on a real team: what actually changes. (AI, September 3, 2026)
The code arrives faster than anyone can read it. That moves the bottleneck, and the job, somewhere new. A practical account of what to change in review, testing and responsibility. - What a penetration test actually finds. (Security, August 13, 2026)
Not film-style hacking. The same handful of ordinary mistakes, in almost every system, and the way they join up into something serious. - One codebase, every screen: the truth about cross-platform mobile. (Mobile, July 9, 2026)
Write once, run everywhere has been promised for decades. The modern frameworks finally come close. Here is what they deliver, what they do not, and how to choose. - You cannot fix what you cannot see: why APM matters. (Engineering, June 11, 2026)
Your servers say everything is fine. Your customers say checkout is slow. Application performance monitoring is how you find out who is right, and why. - Ship every day without breaking production. (Delivery, May 14, 2026)
The safest teams release most often. Their secret is separating two things most companies treat as one: putting code into production, and letting customers see it. - Stop babysitting servers: the case for container apps. (Cloud, April 9, 2026)
Every server you run is a small job you never applied for. Managed container platforms take most of that job away. Here is what you gain, what you give up, and how to move. - If it is not in code, it does not exist. (Cloud, March 12, 2026)
Clicking through a cloud console is the fastest way to build an environment and the slowest way to run a company. The case for infrastructure as code, and how to adopt it without stopping the world. - Choosing a database: when one is enough, and when it is not. (Data, February 12, 2026)
There are hundreds of databases and most products need exactly one. How to pick it, and how to recognise the moment a second one earns its place. - Eating the monolith, one slice at a time. (Architecture, January 15, 2026)
Rewrites fail. Slicing works. How to carve services and micro frontends out of a legacy system, with each new piece able to run on its own or plugged back into the old application. - Technical debt is a balance sheet. Start reading it like one. (Leadership, December 11, 2025)
Engineers say the code needs work. The board hears a request to stop delivering. A ledger of what you owe, what it costs and what to repay ends that argument.