· Post
We are ZERO months away from any good engineer launching their own product
AI is not making good engineers obsolete — it is making engineer-led startups feasible right now, not in six to twelve months.
Insights
Thinking in public
These are posts from LinkedIn. Read them here, then use the discussion link on each article to join the conversation on LinkedIn.
· Post
“Product engineer” seems to be a fashionable term on posts now that we have AI like we made a sudden discovery of engineers value.
IMO all engineers should have been always been product engineers. Full stop. I love building with AI. I loved it two plus years ago when I first saw what it could do, because I’m an engineer and an architect and care…
· Post
For AI-generated code, targeting volume of tests first makes code changes safer, even if test quality not great.
There has always been debate about the “right” way to test software, unit versus end-to-end, TDD versus tests afterwards, 100% coverage versus sensible coverage. There is no universally correct answer because testing…
· Post
Letting AI review its own code is plain stupid
Accountability in AI-assisted development — why AI should not be the final judge of AI-generated code.
· Post
Problems with AI PRs and code reviews are a self-inflicted problem.
One of the big complaints about AI-assisted development is that AI generates more code than humans can physically review. That can be true. But I think people are looking at the problem backwards.
· Post
Grok 4.7 just thinks too much
Recently I’d settled into a workflow that was working really well: Grok 4.6 for thinking and planning + Composer 2.5 for execution. Switching off Fast Mode also put the…
· Post
Engineers, AI Just Killed Your Best Excuse for Leaving Bugs in the Backlog. Now What?
For decades, engineering has divided responsibility. - Support owns support issues. - Product teams build features. - Platform and Ops own infrastructure and keeps things running. A lot of that separation wasn't...
· Post
Architects were ready for AI before many engineers for good reasons.
More than two years ago, I started looking at AI seriously with my team of architects to generate code. At the time, many engineers around us were wary of it and struggled to see the value. To a lot of people, AI...
· Post
Is AI delivering the engineering gains your organisation expected? A little over two years ago, I decided to get back to writing production
I wanted the advice I gave teams and organisations about AI to be grounded in realty not hype. I’ve learned a huge amount, seen the pitfalls first-hand and worked with engineers making the same transition. A few…
· Post
Engineers' accountability when building with AI
It was going to be about technical debt, backlogs, habits of documenting problems rather than fixing them which is now false economy. Then it turned into a rant. I prefer the rant so here it is.. I have a trigger.
· Post
Imagination, creativity, and a damn load of technical skill.
I love building with AI. After 25+ years as an engineer, architect and technology leader, I know I love building software more than ever now.
· Post
OpenSpec and spec-first AI work, but they don’t fit every team
When I first read OpenSpec, I loved the core idea: requirements in the repository, give agents a persistent knowledge base, keep business intent close to the code. I already do this with other documents like ADRs to…
Loading more articles…