Pod Insights The Agile Daily Standup - AgileDad Is AI Killing My Coding Creativity and Critical Thinking? About this episode Is AI Killing My Coding Creativity and Critical Thinking?“Why solve the puzzle when ChatGPT can solve it for me?”That’s a question I never thought I’d ask myself as a young coder. But today, it echoes louder in my mind than any compiler error. I started coding because I loved creating things from scratch. I enjoyed the frustration of debugging, the thrill of getting something right after failing ten times, and the weird pride that came from staring at a screen for hours to make a simple animation work. But now, with artificial intelligence just a click away, something important is fading: my creativity. How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 To be or not to be, I always thought that was the question. But the question really is, apparently, why solve the puzzle when GPT can solve it for me? All right. That's a question I never thought I'd ask myself, especially as a young developer. So someone passed along this article to me by Vincent Mukabi or Mukabi. I hope I get that right. And it's how AI is slowly, slowly killing my coding creativity and critical thinking. And I thought to myself, where's he taking us? So let's see where he's going because I think this is interesting. He says, I started coding because I love creating things from scratch. I enjoyed the frustrations of debugging, the thrill of getting something right after failing 10 times,
0:58 Speaker 00 and the weird pride that came from staring at a screen for a few hours to make a simple animation work. But now with artificial intelligence, just a click away, something important is fading, my creativity. He goes and lists off some, a numbered list here. So let's go through his list. Number one, I'm becoming dependent instead of creative. These days I find myself reaching for the AI tools before even trying to think for myself. Whether it's writing a function, solving an error, or building a website structure, I let the machine do the thinking. And while that may seem smart, it's actually doing damage. I'm not growing, I'm outsourcing. Let's go to number two. I skipped the learning process. There was a time when I would read documentation, watch tutorials,
1:41 Speaker 00 and experiment with different approaches to understand something deeply. But now I just ask AI for the code, copy, paste, move on. I don't understand the why anymore, just the what. Let's go to number three. Number three says, problem solving, problem solving is not fun anymore. Coding used to be like solving a mystery. There was a joy in hitting a wall, thinking sideways, and finally breaking through. But now that AI gives instant answers, I'm skipping the mystery and killing the magic. How about number four? My code no longer feels like me. This one's interesting. AI code is fast, neat, and robotic. It lacks my personal touch, the style I was slowly developing. I used to take pride in my variable names, my logic, even my messy but meaningful comments.
2:26 Speaker 00 Now, everything feels generic. It's no longer my creation. It belongs to AI. Number five. I don't practice patience anymore. Learning the code requires patience. Failing, reworking, Googling, trying again, it's all part of the journey. But with AI giving ready-made answers, I don't have to wait or struggle. And that's just dangerous. Without patience, I just don't grow. How about number six? I care more about finishing than exploring. Before AI, I tried different ways to write a function, just to learn what worked best. Now, I only care about whether it runs. AI has made me prioritize speed over skill. And that's not the kind of developer I want to be. Let's go to number seven, from creator to consumer.
3:09 Speaker 00 Every time I let AI code for me, I feel like I'm becoming more of a user than a builder. And that shift is scary. If I lose a builder's mindset now, why ever get it back? Number eight. I'm losing my critical thinking ability. AI provides solutions but not reasoning. And when I accept those solutions blindly, I miss out on the most important part of learning, asking why. I don't question, I just copy. And that's how thinkers are made. Number nine. Debugging is a lost art. When something breaks, I don't fix it anymore. I just regenerate it. But the best coders are the ones who know how to debug line by line, patiently tracking down the issue. That's a skill AI is slowly erasing from my hands and the hands of many others. And then number 10.
3:54 Speaker 00 Am I really learning or just making better prompts? This is the hardest question I ask myself. Every time I use AI to solve something, I should have tried myself. I wonder, am I becoming a real developer or just learning how to talk to an algorithm?
4:10 Speaker 00 He closes with AI is not evil. It's brilliant. It saves time, helps with errors and opens doors we never imagined. But if we rely on it too much, I fear I'll lose something priceless, my ability to think, create and grow. Interesting. Let me give you my feedback on this. I feel like I understand perfectly what you're saying. One of the things that I find myself telling to computer science people who are going or new freshmen are going in for computer science is I often find myself telling them to be careful because development is changing. And what I'm finding is developers are starting to lean in more on quality management, quality control than they are on actually writing the code.
4:51 Speaker 00 So the scope of what a developer does and the type of job they have is constantly changing. Much like for a scrum master, instead of it being just scrum master responsibilities, starting to blend with project management and change management responsibilities. And for product owners, you're starting to see product management instead of instead of just product ownership. And these three changes are incredibly important to notate because in 2025, we're seeing these shifts where people are leveraging AI to help them do their jobs more efficiently and more effectively. And what I can tell you is those changes are happening and they are working. So the question becomes, where do you fit into the grand scheme of things? Are you still going to be able to do your job in its current capacity? Or is your job going to be reinvented to be something new?
5:37 Speaker 00 I'm going to close with a thought that I had when I was teaching a whole workshop on AI. And somebody contacted me from the audience and they said they were scared. They felt like AI was coming for their job. And my response back was, quote, AI is not coming for your job, but somebody who knows AI better than you do is. And what I mean by that is it's important for you to latch on to something that you know and run with it the best you can. But don't be intimidated or scared of AI. You need to, you need to treat AI like it's your friend. Because if you treat AI like it's your friend, you're going to learn a lot from it. But the second you start dismantling, fearing, or running away from AI, you're going to quickly discover that you're going to go away just as, just as fast as a line of bad code does. That's going to do it. I hope you enjoyed this episode.
6:20 Speaker 00 If you have a topic you want us to discuss, learn more at agiledad.com. I especially want to thank Vincent for that thoughtful article. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time. Do take care. Bye now.
Previous How To Improve Your Teams Motivation Next 20 Powerful Leadership Quotes That Will Transform Your Thinking Page updated November 7, 2026 · transcript and summary are machine-generated