Why would someone want to learn code when AI does it better and faster?

Why learn math when a calculator can do it? Why read a book if AI can summarise it? Why walk to the store if someone can deliver it?

There is no free lunch. The trade off is you get short term gains and long term cognitive dementia. You become a useless generalist.

You are right. I phrased the title bad, now I'm thinking of not the why, but how to keep learning with the goal of that long term thing and I think the answer is something that I must think about myself... something personal

AI does not do it better. It just does it faster. Sometimes that is useful. Sometimes that is harmful. You would want to learn to code to be able to tell the difference.

> AI does not do it better. It just does it faster.

Untrue for the majority of engineers, and almost all with less than a decade experience.

The AIs will only get better from here too.

I use coding assistants about 7 hrs a day in fields I know backwards and forwards and fields I know not at all.

Ai does NOT do better than a reasonable person. It gets about 80% of the way most of the time. And totally wrong and broken sometimes.

It just writes 10x faster. Once testing, bug fixing, testing again, and manually fixing the occasional huge fuck up im about 5x faster than I was. Things would be even better if I was a better programmer to begin with.

> Ai does NOT do better than a reasonable person. It gets about 80% of the way most of the time. And totally wrong and broken sometimes.

I agree, but you're talking about something you're clearly very competent in. That doesn't mean AI isn't as good as a relatively junior engineer.

It also says nothing about AIs of the future. 2 years ago AI could hardly do any tasks without a huge amount of human assistance. Now most SWE will tell you they don't even write code anymore. Let's give it another 2 years.

> less than a decade experience. Yeah, obviously I have less than a decade of experience, and the thing is I can't see how I progress. It's like AI upgrades people even if they are bad, so I don't know if I'm really good or becoming better or it's just AI. I'm practicing for a competition, they said we can use any AI we want. Later we had to use Gemma 3 and oh god, the scores lowered very, very much. The thing is I knew that I'd run into problems without AI, and since using it I forgot what I learnt, from important abstract and theoretical concepts to boilerplate code. But others were using it and our progress was monitored in time-limited competitions, and AI was really good at speeding us up so if you didn't use it you'd be the last person all the time.

It depends on the type of task and the developer's level. For typical CRUD tasks, I'd say AI is often already faster and better than an average developer. But as soon as ambiguous requirements or architectural trade-offs appear, the situation changes

Speed itself also changes the equation. If I can try out five implementation approaches in the same time I used to spend writing just one, the overall quality of the project could very well improve.

Faster? Maybe. Better? Ha. If you honestly think the code quality and perf of AI's code is better than a half-decent human engineer then you're in the wrong line of work. Or you're just an AI bot...yep, that one.

It's just that when I was exploring different things, I really liked front-end and I put more time on that. Recently I used google AI studio, and it designed the thing very well, and I sucked at designing and slow in developing. In other areas, it helped me a lot, for example Laravel docs looked hard to learn for me and I just used php or node js or Django or whatever to avoid Laravel instead, but then I just wanted to prototype some idea, and I used AI, and first I was blindly copy pasting, then I started learning and that was good. But it doesn't happen everywhere. Of course I'm not saying "AI is gonna take programmers place" or something like that.

do what you enjoy and ride out the bubble, remember, ai is only regurgitating and could never make another hubble, you learn by working at the problems through struggle, after enough work, you will no longer be a computing muggle.

Yeah, that's what I think I can do, until I reach the place to be decent enough and find out why we need to code!

We have problems; We use code to solve them; We have a good time.

If you do not feel the drive to code for the fun of the game, then don't do it. I once met a guy who had been doing programming for at least 7 years of his life, 5 as an intern and 2 as a job. He quit because he was in it for the money not for love of the game. He found more fulfillment teaching.

There is not enough time on this earth to waste years on things that we do not enjoy.

If programming were just about typing text, the profession would have disappeared already. In practice most of the work involves understanding requirements, analyzing constraints, finding trade-offs, and fixing problems before they hit production. AI is still noticeably worse at all that than it is at generating code.

At the end of the day it's just a tool. If someone enjoys building things, AI expands their capabilities rather than taking them away. Right now one developer can put together what used to require a small team. To me that sounds like an argument for learning it, not against it

If you genuinely enjoy building, then I think you should just focus on building and not worry about the code. If you can get the results you want without caring, then just do that.

Anything you learn that has any value (which is very little these days) will soon become worthless as AI continues to improve.

If you're learning to code because you're a problem solver like myself, and you enjoy challenging your mind, then this isn't the field for you anymore.

I'm looking to retire soon because I feel like I have no professional purpose as SWE anymore. I used to enjoy building things, but I think that was because I liked the challenge of building things that were difficult, and I don't find any aspect of working with AI challenging really.

Even before you starting coding, just knowing how to do something complicated the right way used to be hard.

There are problems where if you can't figure out the math or don't know the algorithms in the field, then you basically cannot solve the problem. You don't even really know what you're looking for.

Today if you're trying to solve some complex scheduling problem you can just ask an AI and it might crap out a genetic algorithm, or if you need to align two objects in 3D space you can ask an AI and it will crap out an implementation of the Kabsch algorithm. You don't need to know how they work or the math behind them. You don't even need to know they exist.

I would hate for you to waste as much time as I have learning useless stuff.

Ask yourself why you want to learn to code, and pursue that in a more valuable way.

I hope for a strong reason to be found for actually knowing stuff exist and understanding them. That was the fun part for me too, specially after solving a problem so bad and then after a long time ranging from a month to a year, finding out it's known thing that has a name and you can solve the problem so much easier!

- Like every muscle, doing it by yourself, develops your brain's thinking abilities.

- Yes, AI can do whatever the brain can do, but that doesn't develop it.

- What sets humans apart is the ability to think about a situation and do something about it. The ability to think sets us apart. That ability should be developed regardless of what AI can do.

- AI could be better. So what? Comparing yourself with others is the root of disappointment and dissatisfaction. Compare yourself with yourself. Are you better today than you were yesterday?

- Competing with AI is an ever losing battle. Don't compete with AI. Develelop yourself.

AI is horrible at brainstorming and giving ideas and creative stuff like that I think that's the only place I can say any human is better. Yeah developing sounds good. I found some stuff AI can make something like. Like ncase interactive lessons and some other nice web 1.0 stuff. It's just I'm trying to reverse engineer those and they are so creative I don't know how the hell I should even copy them. (said copying because copying is easier than anything else, but even that's hard!)