The Startup CEO blog

In Part I of the series, we talked about vibe coding basics, in Part II, about how to get setup, in Part III, the build, and in Part IV, testing.

In Part I of the series, we talked about vibe coding basics, in Part II, about how to get setup, and in Part III, the build.

In Part I of the series, we talked about vibe coding basics, and in Part II, about how to get setup.

In Part I of the series, we talked about what vibe coding is and how to figure out what you’d build (and if you should build something.

I last wrote code in 1980 on a TRS-80 or a Commodore 64, I forget which, but alas it doesn’t matter!

There’s a fundamental truth about AI that most people don’t think about enough: the transformer architecture — the engine underneath ChatGPT, Claude, Gemini, all of them — is predictive by nature.

In Part I, I curated a lot of big picture articles about AI and society.

There’s a narrative gaining steam in the AI discourse that goes something like this: coding assistants are getting so good that we won’t need software engineers anymore.

Sometimes when I’m mentoring an earlier-career founder/CEO, I cover a topic and think “I must have written a blog post about this, or a chapter of Startup CEO or CXO or Boards, in the past…” and then am shocked to discover later on that I haven’t.

Yesterday I published a five-thousand-word roadmap for fixing America’s broken political system (the Small).