To AI or not to AI.
Some things I will write with AI, using AI, but one thing I promise.... Every single journal entry I will proof read, probably tweak, and probably change to my voice...
Half-formed thoughts, weekly build logs, slow lessons. Updated when I have something worth posting — not on a schedule.
Some things I will write with AI, using AI, but one thing I promise.... Every single journal entry I will proof read, probably tweak, and probably change to my voice...
Things I'd tell him about the year after the exit, the silence, the slow rebuild, the part nobody warns you about.
The version of Kraken I'm building in 2026 is not the one I pitched in 2024. I want to write down why, before I forget the difference.
Distilled from a decade of doing it wrong. The ones nobody really tells you because they sound either obvious or terrifying.
A decade-old codebase is a love letter from a stranger. How I now write code I expect someone else to inherit on day 1.
If you need a daily ritual to find out what people are doing, the problem isn't communication — it's that nobody knows the plan or it's because a mindset was put there due to AI production over the team, the transformation cemented the practice instead of liberating the understanding of where the focus should be... team and collective-accountability
The week my CTO told me my codebase was holding the team back. He was right. Three reframes that helped me move past it.
Everything I knew about building software has a shorter expiration date now. Here's what I'm letting go of — and what I'm keeping.