If you spend time on places that attract newbie programmers (some subreddits focused on game dev or game engines, for example) you’ll see the outcome of “I no longer think you should learn to code.” And it’s not pretty. Many, many posts of people looking for help fixing AI-generated code because the AI got it wrong and they have no idea what the code even does. Much of the time the problem is simply an invented metho…
If anything, debugging gobbledygook an AI wrote is good practice for debugging gobbledygook John from 4 years ago wrote.
Learn to code, ignore AI, then use AI to code even better
51–60 of 150 posts
Re: Learn to code, ignore AI, then use AI to code even better
#52The rise of tools like Cursor reminds me of the Industrial Revolution in France. When machines first appeared in factories, unskilled workers who didn’t understand how they operated often got injured - sometimes quite literally losing fingers. But for skilled craftsmen, these machines became force multipliers, dramatically increasing productivity and improving overall living standards. The same applies to software de…
> But for skilled craftsmen, these machines became force multipliers, dramatically increasing productivity and improving overall living standards.
I don't know if I agree with this line of thought (is there evidence this is true?). Once you have a metal press, you precisely no longer need a blacksmith skilled at swinging a hammer; in fact, all you need is someone that can be trained to read the manual and follow the instructions -- the exact opposite of a skilled tradesman.I do think it is like an industrialization of software engineering[0], but I don't think it favors the skilled craftsman; rather it shifts the sets of skills required and focuses more on reading code rather than writing.
[0] https://coderev.app/blog/ais-coming-industrialization-of-cod...
Re: Learn to code, ignore AI, then use AI to code even better
#53If you spend time on places that attract newbie programmers (some subreddits focused on game dev or game engines, for example) you’ll see the outcome of “I no longer think you should learn to code.” And it’s not pretty. Many, many posts of people looking for help fixing AI-generated code because the AI got it wrong and they have no idea what the code even does. Much of the time the problem is simply an invented metho…
> a problem that is trivially solved by the error message and documentation Then why does the AI not solve it anyways? I think understanding "the code" will eventually be as important as understanding machine code or assembly nowadays - still very important for a small number of devs, important in very rare cases for some other devs and completely irrelevant to the majority of devs.
Re: Learn to code, ignore AI, then use AI to code even better
#54Earlier quoted context omitted.
I have played around wit AI code from time to time. I do not code routinely but I have pet personal projects that allow me to do some code and this is where I experimented. Rule number 1 and the only rule: You need to be a subject matter expert. Be it program logic or be it programming language. AI is only a helper, it will go wrong, frequently, and if you do not understand the reason for the code and the programming…
> Rule number 1 and the only rule: You need to be a subject matter expert. Strong disagree. I've been coding for 25+years but never on the front-end side. I couldn't write JS w/ pen & paper with a gun against my head. But I know what to ask and how to make sure a react component does what I want it to do, with these tools.
That is the subject matter expertise that many lack.
Re: Learn to code, ignore AI, then use AI to code even better
#55Re: Learn to code, ignore AI, then use AI to code even better
#56Anyway, resistance is futile. You will be assimilated ... or retired. The reality of our job is that new generations are going to come in and they'll be using all the latest tools and gadgets. That's nothing new. And I'm part of a generation that in a decade or two will be mostly on the sidelines enjoying retirement. So, I'm well aware that progress isn't going to stop over my whining and grumbling. It annoys me when I catch myself doing that. I want to be better than that.
LLMs are part of the job now. They are tools. And tools are only as good as the people wielding them. So, skill up and learn. It's not like it's very hard. If you are getting poor results, you might be doing it wrong. Figure it out; part of the job. Your mileage may vary. But there are a lot of tools and chances are you just haven't found the right one yet. Also, if some tool/llm limitation is blocking getting good results for something, wait 3 months and try again. The pace of progress is ridiculous currently.
Or better yet: become part of the solution and make your own tools. This stuff is stupidly easy. It's prompt engineering with some trivial plumbing around them mostly. And you can generate the plumbing (what, you were going to do that manually?). That's why there are so many AI tools popping up right now. Most of them won't survive very long. But there are some good ideas lurking there.
Re: Learn to code, ignore AI, then use AI to code even better
#57If you spend time on places that attract newbie programmers (some subreddits focused on game dev or game engines, for example) you’ll see the outcome of “I no longer think you should learn to code.” And it’s not pretty. Many, many posts of people looking for help fixing AI-generated code because the AI got it wrong and they have no idea what the code even does. Much of the time the problem is simply an invented metho…
I have played around wit AI code from time to time. I do not code routinely but I have pet personal projects that allow me to do some code and this is where I experimented. Rule number 1 and the only rule: You need to be a subject matter expert. Be it program logic or be it programming language. AI is only a helper, it will go wrong, frequently, and if you do not understand the reason for the code and the programming…
Unless you're using a LLM with really long context, it's prone that some context loss will happen soner or later - when that happens, pointing errors that dropped out of the context will just result in repeated or garbage output.
Re: Learn to code, ignore AI, then use AI to code even better
#58If you spend time on places that attract newbie programmers (some subreddits focused on game dev or game engines, for example) you’ll see the outcome of “I no longer think you should learn to code.” And it’s not pretty. Many, many posts of people looking for help fixing AI-generated code because the AI got it wrong and they have no idea what the code even does. Much of the time the problem is simply an invented metho…
Subreddits focused on gamedev have long stopped being about the craft itself, unfortunately. 90% of the posts are about marketing or are self-help/motivational. Anything related to art, sound or programming barely gets upvotes.
Re: Learn to code, ignore AI, then use AI to code even better
#59The downside is that at the current speed of improvement, AI might very well already be at escape velocity, where it improves faster than you, and you'll never be able to catch up and contribute anything useful. For a lot of small hobby projects, that's already the case.
I don't think there are any easy answers here. Nothing wrong with learning to code because it's fun. But as a career choice, it might not have a lot of future, but then, neither might most other white-collar jobs. Weird times are ahead of us.
Re: Learn to code, ignore AI, then use AI to code even better
#60Earlier quoted context omitted.
I have played around wit AI code from time to time. I do not code routinely but I have pet personal projects that allow me to do some code and this is where I experimented. Rule number 1 and the only rule: You need to be a subject matter expert. Be it program logic or be it programming language. AI is only a helper, it will go wrong, frequently, and if you do not understand the reason for the code and the programming…
> Rule number 1 and the only rule: You need to be a subject matter expert. Strong disagree. I've been coding for 25+years but never on the front-end side. I couldn't write JS w/ pen & paper with a gun against my head. But I know what to ask and how to make sure a react component does what I want it to do, with these tools.
> Rule number 1 and the only rule: You need to be a subject matter expert. Be it program logic or be it programming language.
You are a subject matter in program logic, just not programming language. You are supporting their point, not disagreeing.