A few months ago, I realized I hadn’t written a regex by hand in weeks. Not because I suddenly stopped needing them — but because ChatGPT wrote eve...
For further actions, you may consider blocking this person and/or reporting abuse
NICE one... it hits hard because I feel ive became duller or at least lazier to debug one by one.
but in some cases it really needs my OWN EFFORT to find the correct answer. after consuming more than 70% context some AI tends to be hallucinating and repeat the wrong solution in cycle
Absolutely agree, I’ve noticed the same. Sometimes AI gives a confident wrong answer, and we get stuck trusting it too much.
I like how you put it: it still takes our own effort to debug and verify. That’s exactly where the real learning happens — not in the first result, but in checking why it’s right (or wrong).
Great article!
I still believe it's up to us, developers if we get dumber or smarter. Tools have nothing to do about that, it's all about how we use them. Delegating way too much to AI will definitely make our analytical mind rusty; however AI tools, if used wisely and effectively, can actually make you a smarter engineer than you were before.
When I talk about this stuff, I like to use a car driving analogy. It's like saying automatic gearboxes in cars cause more accidents, as drivers have more freedom to do other stuff like texting or scrolling the social media. However, it's not the car, it's the irresponsible driver that has no idea how to drive the car safely.
Love that analogy, the car one is spot on.
100% agree: it’s not the tools, it’s how we use them. AI can either make us sharper or softer depending on how conscious we are.
I like to think of it as using AI as a copilot, not an autopilot.
I always say this to the gen Z developers "Try before you ask. Solve it yourself first, then compare your answer with the AI’s."
For experienced developers and leads: You can ask AI to write code, but make sure you validate the code is right and well optimized.
I learned so much new awesome things I wouldn't even thought about before thanks to AI in last year. I disagree with the tips. Don't be shy to let AI scaffold the draft of a solution as a first step. The key to stay in game is not just copy-paste the answer blindly, but always think about the proposed code, understand it fully, ask for details and reason about the decisions you find suspicious ("What does this line exactly do?", "Why you used this setting?", etc). Also, having to write the prompt in such a way AI understands the task good enough to spit a working solutuion is ultimately making you a better developer (and thinker).
Knowing all the JDK API methods' signatures by heart is also not making you a better developer (although Oracle exams when I did them used to pretend otherwise). You need to know what is available and how (not) to use it. Best engineers in the world were always googling (and now chatGPT-ing) stuff like "How to center a div?", because their value added was in the fact they knew *WHY * they want to center it. Fill your mind with performance, security, UX, accessibility concerns - those are important. Skills of manually writting a code not that much.
That’s an awesome perspective, and I agree with most of what you said.
I think we’re saying the same thing from different angles: the danger isn’t in using AI, it’s in using it unconsciously.
You’re absolutely right, prompting well, questioning the output, and understanding why the AI chose something are skills in themselves.
My post was more about the moments when we skip those steps entirely.
In short: AI can definitely make us better developers. As long as we stay the ones doing the thinking. 🙌
Nice one. Currently, most clients say that AI can give better results, but they don’t realize that AI can sometimes provide incorrect answers and information. This post is helpful for developers because AI does not replace the work developers do
Totally agree. I think the danger isn’t that AI gives wrong answers — it’s that it gives convincing wrong answers.
Developers who stop questioning the output are the ones who’ll fall behind, not the ones who use AI wisely.
can you give some tips mastering programming without ai
Try to solve problems manually first, even small ones.
Rebuild something you already know without AI, then compare your approach to what AI would suggest.
It’s not about rejecting AI, it’s about keeping your brain in the loop.