The Python Coding Stack: Doubling Down on Python in The Age of AI

Properly. And I wanted to share where I’ve landed, because I think the answer matters and it’s different from what some hot takes suggest.Do I still need to learn to code?The way we write computer programs is changing. I don’t have a crystal ball for what programming looks like in five or ten years.But here’s the thing: neither does anyone else.Here’s what I know from watching others and experimenting with AI tools in my own work: right now, the people getting the most out of AI are the ones who already know how to code.Here’s the hierarchy as I see it today:Where we stand today:No coding knowledge = Little benefit from AILittle coding knowledge = Intermediate benefit from AIIntermediate coding knowledge = Great benefit from AIGreat coding knowledge = Superpower-like benefit from AIWe’re in an era where some coding knowledge takes you much further than it could have a few years ago. That’s not an argument against learning to code. It’s an argument for it.“But what about those vibe coding people? They seem to be shipping things.” Some are. I’ll be honest about that.The projects I’ve seen from pure vibe coders tend to be smaller, tend to follow well-trodden patterns, and often hit a ceiling when something goes slightly wrong or slightly off-piste. Which is fine for a side project. I just created a useful dashboard to help me organise my day the way I want to using this approach.But it tells you something: the AI does the heavy lifting on the known stuff. The moment something needs genuine thinking, you need the human who knows what’s going on beneath the surface.AI-Assisted Human Coding and Human-Assisted AI CodingMost serious work right now is a partnership.Sometimes it’s AI-assisted human coding. The human drives, AI assists.Sometimes it’s human-assisted AI programming. The AI writes most of the code, but the human knows what to ask for, how to steer it toward good design, how to evaluate whether the output actually makes sense.Even when the coding looks like it’s done by AI, the person prompting and reviewing it is generally an experienced programmer. They’ve learned enough Python to know what’s reasonable, what’s a red flag, and when the AI is confidently wrong.I’ve been experimenting with agentic AI over the past few weeks. I’ve tackled side projects I’d never have had the time for before. I didn’t have the time to start then, let alone finish them. Some of that output will show up in other places — stay tuned! But not here. The Python Coding Stack is the place for my writing.The Programming Mindset When Talking to AI AgentsHere’s one thing I noticed. Talking to AI agents isn’t like talking to humans. But it isn’t like talking to computers (a.k.a. programming) either.You need both qualities at the same time.You need the clarity and communication skills you’d use with a person — explaining context, setting direction, knowing what matters, using clear language.And you need the precision you’d use when programming — no ambiguity, clear intent, structure.A good programmer who’s also a good communicator is the best human to work with AI agents.That’s not coincidental. The same thought habits that make you an effective programmer also make you an effective prompter and reviewer when AI is involved.I’ll share some of the prompts I’m using in a future post and analyse them to discuss why I wrote what I wrote. Learning to code well gives you an unfair advantage in this new world.There’s Never Been a Better Time to Learn PythonHere’s what I’ve convinced myself of after all this. There’s never been a better time to learn Python.A few years ago, you needed to reach an intermediate-to-advanced level before you could do something genuinely useful with Python. The bar was high. Now, with AI assistance, the bar is lower. Less Python knowledge takes you further than ever.What used to need expertise can now be explored with curiosity and a bit of intermediate-ish-level Python.That’s not replacing deeper learning. It’s making the entry point more accessible. And once you’re in, you can go as deep as you want.So yes, I’ll keep coding in Python. Sometimes with a bit of help from AI. Sometimes with a lot of help from AI.And yes, I’ll keep writing about Python here, as I’ve always done.The Fun FactorHere’s the thing we don’t talk about enough when discussing programming. It’s fun. It’s challenging. It’s rewarding. It’s fulfilling. It’s stimulating. It keeps my brain active.I code because I enjoy it. I’ll keep writing about Python because I enojoy that, too,, and because I find value in sharing here — for myself and, hopefully, for you too.Normal service resumes here. More Python posts coming. And maybe, just maybe, some of the AI things I’m learning will make their way in, too.Psst–did you know you can become a premium member to be a part of The Club? It would mean so much to me!Subscribe nowQuick question:Photo by Maksim GoncharenokJoin The Club, the exclusive area for paid subscribers for more Python posts, videos, a members’ forum, and more.Subscribe nowYou can also support this publication by making a one-off contribution of any amount you wish.Support The Python Coding StackFor more Python resources, you can also visit Real Python—you may even stumble on one of my own articles or courses there!Also, are you interested in technical writing? You’d like to make your own writing more narrative, more engaging, more memorable? Have a look at Breaking the Rules.And you can find out more about me at stephengruppetta.com