Test-n-Tell - tiny apps, Big ideas

  I've been doing a lot of vibe coding lately, and one tech stack emerged for me as the most practical. Spoiler alert 1: it's Firebase + Codex + Google Cloud. Spoiler 2: tomorrow it could change.

One of the most common leadership anti-patterns in modern organisations is this: A high-performing individual contributor gets promoted into management… …and continues competing with their team on execution.

“Vibe coding”, building software by describing intent and letting AI generate, refactor, and orchestrate code, is quickly evolving into something more powerful: agentic coding. Systems that don’t just autocomplete code, but reason across files, plan changes, run tests, deploy, monitor, and iterate. If this trajectory continues, we are not just accelerating engineering. We are reshaping the entire product value chain.

  As AI moves from experimentation to production, many organisations discover that “adding AI” is not a feature - it is a fundamentally different product problem. This realisation has led to the rise of the AI Product Manager (AI PM).

  What is the difference between platform PM and any other? Is there a difference? Do platforms even need PMs, and how many?

  Everyone who has ever tried to create a product has their embarrassing failure story. Here's one of mine.

  I used to love football! Watch it, play it, suffer from chronic underperformance of my fantasy team... It's during one of the games that I thought about how football could be a good metaphor for the business of building software products.