Agent-ready is the new mobile-ready
The companies that designed for mobile beat the ones that bolted it on. AI agents are the same shift, and five questions tell you which of your tools are ready.
Want a quick email when a new article is published? Subscribe
The companies that designed for mobile beat the ones that bolted it on. AI agents are the same shift, and five questions tell you which of your tools are ready.
Jira, Confluence and Atlas each held a slice of the picture at a different level of detail, so every week someone rebuilt the whole thing in PowerPoint.
Your strongest engineers lose Friday afternoons to reports that people skim at best. Transparency should come out of the work, not sit on top of it as a second job.
Building the product was the easy part. Why giving most of it away is a commercial decision, not the absence of one.
The complete operating model I'd bring to a product and engineering organisation: squad structure, every role defined, sprint and release process, DevOps principles, product tiers, AI use cases, and how the whole thing flexes down for smaller headcounts. Twelve documents, written to be used rather than admired.
Whether agent-built software replaces a SaaS product depends on what that product actually sells. Three categories, and what each one means if you're writing cheques.
The cost of an AI feature is set by its design, not the price of the model. A pilot can't show you the difference, and the pilot is when the design gets fixed.
The engineers most resistant to AI coding tools aren't who you'd expect. And the gap between those using them properly and those refusing to look is widening at a pace that should worry anyone planning a career in this profession.
Your team's internal tools backlog is the perfect low-stakes proving ground for AI development. Here's why, and how to make it happen.
The cost of baking observability in from day one is close to zero. The cost of not having it can be measured in missed deadlines, lost revenue, and sleepless nights.
Much of software development is well understood. Smart teams, good communication, building the right things. But what about the parts that aren't in the online textbook?
A peer-reviewed study puts numbers to the AI coding debate. The results might surprise the sceptics.
Cutting through the noise on AI-assisted development, for people who need to make decisions about it.
When your tech team blames slow progress on 'context switching', they probably mean something else entirely.
A peek behind the curtain of PE/VC technical DD. What raises red flags, what impresses, and how to prepare.
Aviation has spent a century formalising how to handle human error. It is time software engineering caught up.
Most companies have spent 18 months playing with LLMs and have nothing to show for it. The problem isn't the technology.
Goodhart's Law in action: why measuring the wrong things destroys teams, and what to do instead.
Moving fast doesn't mean breaking things. It means building the ability to turn them off in seconds.
Stop treating onboarding as a series of coffee chats. If your new hire hasn't shipped to production by day two, you're already losing money.
When production fails, the pressure to find a 'why' often gets in the way of finding a 'how'. Here is how to manage the chaos.
Translating technical reality into board-level conversation. What to say, what to skip, and why a live demo beats a slide deck.
We've had five years to figure out remote work. Most companies are still pretending it's temporary.
It's not always bad. Why your CTO should be borrowing against the future.
Why hiring people on the basis of them having worked in the industry before, or explicitly used a particular tech stack, isn't always the best plan.
Why your engineering team isn't just 'typing' and why a single misplaced space can bring a platform to its knees.
When building gets cheaper, the finances change completely
AI handles the typing. The hard part was never the typing.
The risks are real. They're also familiar, and manageable.
Your developers are probably already using these tools. The question is whether they're doing it intentionally.
Your developers are probably already using these tools. The question is whether they're doing it intentionally.