I see Flow Coding as the reasonable middle ground which will become mature in no-time.
We hear about Vibe Coding everywhere. This is so different from what we have done for decades now. So, it might take too much attention right now, and things like Flow Coding aren’t in focus. I see Flow Coding as the reasonable middle ground, that will mature quickly.
Staying in the flow of coding is great in many ways, but not being in the flow of coding would be rather nasty.
We are not alone anymore
Interestingly, we aren’t doing this alone as humans but with AI coding tools. While we heard many bad things about the quality last year, things have shifted towards keeping quality rapidly overnight. So rapidly even that many Software Engineers still keep telling the old phrases:
AI Codes for you in 1 hour your app you and you debug it for the years to come.
AI creates garbage code.
AI degrades your own skills and makes you dumb.
To mention some of the general ideas. But are those still viable?
I don’t think so. AI moves faster than the human being can grasp right now.
I have been using Claude Code in production for over a week, which totally changed my mind.
"After 32 years of writing code, I sat there, watching Claude Code do my job while I just pressed Enter. And the scary part? It did it well."
When I Realized the Shift Had Already Started
There are moments in your career that feel like turning points.
Mine happened while testing a migration on a large-scale Next.js frontend. I wasn’t exploring AI for fun or toying with prompts; I was doing real work on real code and letting Claude Code take the lead.
I’ve built software since the 1990s, from BASIC on C64 to web stacks and massive SaaS platforms. I know how migrations go: Messy, slow, and painful.
But this time was different. The AI understood the task, handled edge cases, adjusted to patterns, and even debugged problems it encountered. I was no longer writing code. I was reviewing someone else’s—except that someone wasn’t a person.
And that’s when it hit me: the future of coding isn’t about typing anymore. It’s about thinking, guiding, and reviewing.
The execution?
That can be handled by machines.
What Makes Coding AI Actually Work
The magic doesn’t happen automatically. You need a foundation.
Here are the essential requirements if you want to work effectively with tools like Claude Code:
Good Architecture
A clean, modular codebase allows the AI to reason across files. Spaghetti code? Forget it. Claude can only help if your code is already structured well.A Strong Typing System
TypeScript strict mode isn’t just good for you—it’s critical for AI. It provides guardrails that help the model understand constraints, infer intentions, and validate changes.Project Guidelines
Claude Code reads yourclaude.md(or equivalent) and adheres to project conventions. Folder structure, import order, naming patterns—it all matters. Define the rules, and the AI will follow.Testing Strategy
If you don’t have automated tests, you’re flying blind. TDD, component-level testing, and end-to-end checks let you trust what AI changes.Experience Still Matters
AI is powerful, but it isn’t intuitive. You need to catch subtle issues, architectural misalignments, or overconfident shortcuts. Your judgment is still the safety net.
Key Takeaways
Claude Code isn’t just a prompt-based tool. It acts like a junior developer who learns fast and works with context.
Flow Coding is the future. Let AI handle the typing and jumping between files while you stay in flow, guiding strategy and verifying.
This changes energy dynamics. You don’t end a session mentally drained. You end with more creative bandwidth left.
Tooling is catching up. With editors like Cursor and assistants like Claude, we’re seeing the rise of AI-native development environments.
We’re still needed, just in a different role. Review, design, and decision-making are the new primary skills.
My Personal Conclusion
If you're a podcast listener like me, here’s the takeaway:
We’re moving from coders to curators. And the sooner we adapt, the more we can lead this shift—rather than get run over by it.
The next generation of developers will grow up with Claude in their terminal, not VS Code alone.
Are you ready for that?
👉 Let me know what you think. Would you trust AI with your codebase?
Adrian
Share this post