alt Hacker News> One major problem I see with the use of AI is that it will prevent people from building an understanding of <insert problem domain X here>.
I don’t really think this is a problem. AI is a tool, you still learn while using it. If you actually read, debug and maintain the produced code, which I consider a must for complex production systems, it’s not really that different compared to reading documentation and using Stack Overflow (i.e., coding the way it was done 10 years ago). It’s just much more efficient and it makes problems easier to miss. Standard practices of AI assisted development are slowly forming and I expect them to improve over time.
Replies
> AI is a tool
A more helpful analogy is "AI is outsourced labor". You can review all code from overseas teams as well, but if you start to think of them as a tool you've made too big promotions into management.
> It’s just much more efficient and it makes problems easier to miss. Standard practices of AI assisted development are slowly forming and I expect them to improve over time
Bravo! IMHO, AI just underscores core high quality engineering practices that any high quality engineer has been practicing already.
AI is a tool that provides high leverage - if you've been following practices that allow sloppy coding, AI will absolutely amplify it.
If anything, I would guess that the AI assisted future will require engineers to think through the problem more upfront and consider edge cases instead of jump and type out the first thing that comes to mind - the AI can spit out code way faster.
There's an alternate, vibe coded universe where engineers just spit out slop but as I wrote in another comment here, there are tools to detect that. These are tools that sound "enterprisey" and that's because before AI, no one else had to deal with such scale of code - it's was just far too expensive to read, update and create PRs.
Those boundaries are coming down and now almost everyone who can pay for Oxygen tanks have a shot at scaling Mt. Everest.
I’ll bite - I’ve been a dev at a new company for about a year and a half. I had mostly done front end work before this, so my SQL knowledge was almost nonexistent.
I’m now working in the backend, and SQL is a major requirement. Writing what I would call “normal” queries. I’ve been reaching for AI to handle this, pretty much the whole time - because it’s faster than I am.
I am picking up tidbits along the way. So I am learning, but there’s a huge caveat. I notice I’m learning extremely slowly. I can now write a “simple” complexity query by hand with no assistance, and grabbing small chunks of data is getting easier for me.
I am “reading, debugging, and maintaining” the queries, but LLMS bring the effort on that task down to pretty much 0.
I guarantee if I spent even 1 week just taking an actual SQL class and just… doing the learning, I would be MUCH further along, and wouldn’t need the AI at all. It’s now my “query tool”. Yeah, it’s faster than I am, but I’m reliant on it at this point. I will SLOWLY improve, but I’ll still continue to just use AI for it.
All that to say, I don’t know where the future goes - our company doesn’t have time to slow down for me to learn SQL, and the tool does a fine job - it’s been 1.5 years and the world hasn’t ended, I can READ queries rather quickly - but writing them is outsourced to the model.
In the past, if a query was written on stack overflow, I would have to modify it (sometimes significantly) to achieve my goal, so maybe the learning was “baked in” to the translation process.
Now, the LLM gives me exactly what I need, no extra “reinforcement” work done on my end.
I do think these tools can be used for learning, but that effort needs to be dedicated. In many cases I’m sure other juniors are in a similar position. I have a higher output, but I’m not quickly increasing my understanding. There’s no incentive for me to slow down, and my manager would scoff at the idea, really. It’s a tough spot to be in.