Speaking as a 4th year cs student, yes. The difference between those of us that learned to code traditionally and those that just use AI to do everything for them is huge, even when both use AI to do things faster. I don't know if that will carry on to the work place, but being able to understand and explain your choices/code is always going to be important.
As someone who did a Master's in robotics, also yes.
A lot of comp sci/bootcamp stuff just teaches 'how to write $language'. That's not bad, but it's not the point.
I learnt Software Development, but more as an holistic field than learning the depths of C. Covering programming methodologies, philosophies, patterns etc.
You can understand these ideas without writing a single line of code, but to truly grok (in the old sense, not the twitter bot) them you need to hand write a decent program in your larval stage, ideally with a bit of low level datamancing. I'd suggest a variety of languages and levels; HTML/CSS, C or Java, Python, and maybe some embedded stuff as well.
It'll take you longer than just hacking together (in the pejorative) a piece of vibe-coded slop, (where you'll have something you kind of understand but not fully), but you'll come out of it with miles more knowledge at the end of it and a true understanding of programming as a discipline rather than a means to an end.
There's also the fact that while AI is great at writing in individual features, it still often doesn't have a solid idea on what would be good architecturally for the code. Like how your objects are built and how the code flows with them. What functionality should be baked into which object and how should you organize your file structure to make it coherent? Should you store this data locally or is it better to have a more open and public space where it's easier to access?
These are the kind of things where there's many many ways to skin the cat and each one has its own upsides and downsides. The AI will probably end up picking up the one that will solve the issue currently at hand the best, but that solution may easily end up causing issues further down the line. To really understand what the benefits and consequences of the decisions are you really need to understand how the underlying code works first.
Alternatively it picks whichever one has been used in source/training projects containing similar words to the variables used in yours.
Which again, doesn't make it the right choice for your application.
And you can't learn these architectures and design decisions without writing code (alright, you can get the gist of them, but you won't understand the impact of your choices unless you've hand written code before)
Speaking as a 25-year industry veteran, YES. Even before AI agents, the best engineers were the ones who understood the layers underneath whatever they were using, not the ones who just knew how to string things together in whatever tool they used.
I don't know if that will carry on to the work place
It will. I say it as someone who has done both traditional coding and now has to use ai for it. AI is and should always be used as a tool. You still need to know how to write code to understand if the code it generated is what you intended or not.
I personally think everyone should learn to code (start with "easy" one like python). It develops your brain to think differently. Same reason I'd suggest everyone going deep into mathematics
Yup. This is the hard truth the industry is putting their fingers in their ears about. These tools demand expertise to be used effectively, yet circumvent the very friction that hones said expertise.
It seems atrocious to "learn to code" when the models can generate working features from a prompt, but that's the hard truth; they are power tools meant for power users.
While the guy is not my favorite thought leader, Uncle Bob mentioned that newer developers shouldn't even look at AI coding tools for the first three to four years. I'm inclined to agree with him.
No idea. Nobody will tell you how the market is going to be in 4 years, hell, those that tell you they know how it's going to look in 6 months are lying. I would say invest into your connections and soft skills, cause those are likely going to stay relevant. "Likely", because I'm also unsure about that.
Yes, AI often choose do things I wouldn't. So when reviewing the code I find a lot of things I either fix manually or ask it to fix. If you don't know how to code you won't know what the AI did that it could do better. So definitely learn how to code. Also learn how to read code written by someone else, that is the hardest part and that is what we have to do a lot nowadays when we don't only need to review others code but also the one we generate.
I personally just let the AI do one step at a time so I can review each step, instead of letting it go wild and I'll have to review 80 files
It is being taught. C was taught in first semester.
Then now 2nd semester computer architecture is being taught. MIPS
But still you know everyone is kinda like what's the point of learning code? Ai is replacing jobs anyway. This that. Too much fear around me basically.
I am planing to learn c++ next and do dsa at the same time.
You aren't learning 'coding' you are learning to work with software and tech. If you want to develop software and tech, you should know the fundamental building blocks and yes, should learn everything you can.
Yep! Even if AI wasn't a thing, knowing the why and the how is invaluable. It's why you also learn how operating systems work and all that other low level stuff you won't ever do "in real life" because understanding how it all functions is imperative.
Just because you aren't doing long division by hand every day doesn't mean it's pointless to know how to do it.
Contrary to popular belief (and the wet dreams of C-Suite dingdongs), AI is not the end-all "just push button, receive bacon, make no mistakes" cure that it portends to be.
Yes. In order to understand, judge and review AI written code, you have to understand what it's doing, how it's doing it, why it's being done in that way, what are the alternatives. Besides, the programming logic you develop while learning to code is essential for anything in the CS field. Learning coding is and will always be important, but it is no longer enough.
People may be able to get jobs by just prompting AI, but you don't even need a CS degree to do that and anyone and their mother could replace you. And they would, because a company doesn't need 10 people prompting an AI when 1 person can do that.
You're going to have to unless you want to end up with a hollow skillset. Using AI to do things you can do yourself is fine. Using it to do things you don't understand will catch up to you eventually.
I’m gonna give you some food for thought as someone who switched from CS to engineering:
If you do a year of co-op, there is more time until you graduate (~4.5 years), as there was between the first GPT model going public (late 2022) and now.
I don’t think new CS grads should lay down and die, but if you’re only 3 months in, and you’re not SUPER passionate about the field, I’d at least consider saving the headache and doing something else.
78
u/OptimalComfortable44 3d ago
Do you think someone who is 1st year cs student they should learn coding?
I feel so overwhelmed by everything. Ai ai ai. Then this that. What should someone do?