In Part 5 , I described the compound effect — what happens when trust, depth, breadth, and infrastructure all stack up. I thought that was the end of the story. It wasn't. Somewhere around week seven, I stopped talking to one Copilot. I started assembling squads. (I realize that sounds dramatic — but bear with me, …

Read More

Two months ago, I asked an AI to explain an error message. Last week, I built a complete web application — frontend, backend, authentication, infrastructure, CI/CD pipeline, monitoring dashboards — in a single afternoon session of 122 exchanges. This is the final part of the series (well, almost — more on that in a …

Read More

Eight weeks ago, I accidentally committed a secret to a public repository. Last week, I was designing authentication architectures with managed identities and federated credentials. Same person. Same tool. Completely different confidence level. This post is about the most transformative phase of my journey: when I …

Read More

I hired a coding assistant. Then I realized it's not a coding assistant. It's a thinking assistant that happens to be really good at code. In Part 1 I built the reflex. In Part 2 I learned to go deep. Part 3 is about going wide — and to me, this is where things got really interesting. The category explosion Looking …

Read More

Most people use AI like a search engine: one question, one answer, done. To me, the real power unlocks when you keep going. In Part 1 , I described the reflex shift — replacing Google with a direct question. That's stage one. Stage two is what happens when you stop leaving after the first answer. And honestly, I …

Read More

I spent 20 minutes googling an error message. Then I asked an AI, got the answer in 8 seconds, and spent the next 10 minutes wondering why I hadn't done that sooner. To me, this is a story about trust. Not the blind kind — the calibrated kind. The kind you build one correct answer at a time, and that honestly takes a …

Read More