Engineering leadership for the teams behind lifestyle brands.
The patterns your team feels but hasn’t named yet. Weekly. Free.
Brands I've Built For
What People Say
“Jono is the manager every engineer hopes to work for at least once in their career.”
“Jono may be the most talented technologist I've worked with in my long career.”
“Jono has been my greatest professional accelerant. He provided the framework I needed to grow into a technology leader.”
“A natural born leader ... working with Jono was a masterclass in drive with insane depth of knowledge.”
“Jono excels at building teams and solutions from zero to one.”
“Jono propels any team he is a part of.”
Latest Writing
Your team is prompting from scratch every time. That's the problem.
If I had to roll out AI to my engineering team again, I wouldn't start with the tools. I'd start with one repeatable workflow, map every step, define what good looks like, and turn it into a pipeline that compounds. Here's how that works in practice.
The gap between your senior and junior engineers is compounding in ways most leaders aren't watching.
A junior engineer told me he wasn't sure he understood everything the AI was outputting for him. He was reading it, checking it, shipping it. But he couldn't reliably tell if it was right. That conversation opened a harder question about what AI is actually doing to the engineers who never built the foundation first.
The governance gap nobody talks about when your team ships AI-generated code
Technical leaders are being asked to set AI standards, define acceptable output quality, and govern what gets into production. You cannot do any of that if you've lost your own connection to how your team builds. Here's what the drift looks like, and what it costs you when AI has already doubled your team's output.