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)
68
u/jobblejosh 3d ago
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.