Still in the Code
I lead engineering at a Fortune 100 company, and I still ship my own software. Not because leaders need to prove they can code, but because AI is changing the work faster than secondhand models can keep up.
★tag · 10 essays
All essays tagged ai-coding.
I lead engineering at a Fortune 100 company, and I still ship my own software. Not because leaders need to prove they can code, but because AI is changing the work faster than secondhand models can keep up.
★I rebuilt a working web app as native iOS and Mac software, not because native was magic, but because the discipline required to make it correct is the same discipline AI agents need to be useful.
★The strategy posts say AI software development is a system. Here is the working loop I run inside that system: a refined specification, a layer of standards, and a coordinated set of specialists doing the work.
★After thirteen months of daily Claude Code use, I stopped treating AI coding as a prompt discipline problem and started treating it like an engineering system: configurable, layered, observable, and built to learn.
Every tool in your product development life cycle is now an AI agent trying to do everything. Here is how to stop the chaos, draw the right boundaries, and build an orchestrated pipeline that actually works.
★A decade-old side project, six major features, one week. How spec-driven AI-assisted development compressed months of work into a focused sprint on a real codebase with real constraints — and where the AI got it wrong.
From 'users want commute alerts' to 1,800 lines of shipped, App Store-ready code in a single coding session. A deep dive into architecture, edge cases, and what AI-assisted iOS development actually looks like.
Andrej Karpathy put words to something many engineers are quietly feeling: we have been handed a powerful alien tool with no manual. Where the leverage is actually moving up the software stack — and what that means for the people writing code right now.
From generative AI as a tool to AI as a strategic partner. Reflections on 2025 and what excites me most about 2026.
How my workflow evolved from autocomplete magic to spec driven development, and why trusting GenAI with more of my code has changed how I build software.
browse other tags