Day 0: AI Can Write Code. Someone Still Has to Decide.
June 21, 2026
For the last few months, I haven’t written much code.
I’ve mostly been prompting. Deciding. Planning. Reviewing. Correcting. Arguing with AI. Trying to understand why something worked, and why something else failed. Comparing approaches.
Somewhere in that process, I realized something.
The skill I need to get better at isn’t typing code. It’s making decisions.
Why shouldn’t WebSockets run on serverless platforms? How do background jobs actually work? When should you choose a monolith over microservices? What caching strategy makes sense? How should databases, deployments, security, and frontend architecture be designed?
These are the questions that matter. AI keeps getting better at writing code, but someone still has to decide. Someone still has to understand the trade-offs. Someone still has to ask why.
Even if the industry changes tomorrow, there’s one thing nobody can take away: knowledge. Or curiosity.
People often talk about “survival of the fittest.” What fascinated me about Darwin’s idea was never strength or intelligence. The species that survive are the ones that adapt. In technology, adaptation comes from curiosity, from asking questions, from understanding things deeply enough to make better decisions when the landscape shifts.
Curious people keep learning.
Curious people adapt.
Curious people survive.
That’s what I’m trying to build here. Not expertise in every framework. Not mastery of every tool. An understanding of how systems work and why decisions get made the way they do — the kind that doesn’t expire the moment a new framework shows up.
So I decided to learn in public. Not through courses, not through “build X with Y” tutorials. Just one concept, one question, one architectural decision at a time.
This is that notebook: a place to document what I discover, what I misunderstand, what I change my mind about, and what I learn along the way.
Maybe you’re years ahead of me. Maybe you’re learning right alongside me. Either way, welcome.
Let’s figure things out. And learn it anyway.
What This Series Is
The Architect’s Mindset is structured around 10 topic families — System Architecture, Multi-Tenancy, Access Control, APIs, Data, Frontend, Backend, AI Integration, Infrastructure, and Security. Fifty topics in total. One at a time.
The Roadmap has the full list of what’s coming.
The first real topic is next: Monolith vs. Modular Monolith vs. Microservices vs. Serverless.
If you’re senior to me — I’d love your corrections and guidance.
If you’re junior to me — learn with me.
I’ll be sharing everything here and on LinkedIn.