Methodology, industry takes, and case studies. Three new posts a week. Mostly Janaka. Sometimes the team.
What AI actually changes about every stage of software development — and why the phase everyone ignores is now the most important one.
$ read the postYou did everything 2022 told you to do — funnel, CRM, trust badges, SEO audit, maybe a Webflow rebuild. Inquiries are still flat. You didn't execute badly. You executed a playbook written for a reader who is leaving the building.
Why your best engineer became the bottleneck — and how to spot the same freeze in yourself.
It was a symptom of under-resourced teams pretending breadth was excellence. AI did not create unicorns. It revealed that most of what we called unicorn skills was translation work that never needed a human in the first place.
What the first real data on agentic software development tells us — and what it means for how teams should be working in 2026. 1. The most quoted law in software is…
The traditional PM role isn’t just changing — it’s being structurally replaced from the inside. One person, the right spec, and the right toolchain now does what five used to. Here’s what that actually looks like.
The MVP was always a workaround for expensive software. Vibe coding eliminated that excuse. Here’s why the prototype is now the spec — and why spec-first is the only rational model for what comes next.
Landing page, knowledge base, Chrome extension concept, and a web app funnel — all from a single tax computation spec.
A roster, attendance, and biometric platform for operations managers — spec’d from a spreadsheet problem, not a feature list.
An ethical reputation management platform for Dutch hospitality — built on a 12-hour head start, not a filter.
The conversation about AI-native software development is having the wrong argument.
I raised $100,000, burned $90,000 on development, and shipped to almost nobody. Here’s the ratio I wish I’d known — and why the economics of 2026 have made getting this wrong significantly more expensive.
A mid-market HVAC company went from whiteboard sketches to a working CRM + dispatch + field app in three weeks — without a single requirements workshop.
14 screens. 295 staff. Zero ambiguity. How a specification document became an interactive enterprise prototype.
SAFe felt like enterprise overhead for a 15-person studio. Then we added AI agents to the workflow — and discovered that the coordination layer SAFe was solving for doesn’t disappear when the team is small. It explodes.
AI didn’t create spec-driven development. It just made ignoring it unaffordable.
How structured artifacts living in Git are becoming the operating layer of AI-native software — and why there’s no single right way to do it yet. Field notes from a studio that rebuilt how it works from the ground up.
No posts in this category yet. New ones land every Mon, Wed, Fri.
We don't run a newsletter. New posts land in the RSS feed the moment they ship — Monday, Wednesday, Friday. Pipe it into whatever reader you actually open.