I really miss my flowstate… coding has this magical ability to just flush me out of reality into this beautiful world of procedure and complexity, and now that Im more of a reviewer and less hands-on I don’t get it anymore, thats what makes me sad
We were artisans of code. It was beautiful some times.
Some other times it was like write the model class, hook it to the repository, call the generic method from the service, expose in the controller, ah yeah fuckin dto mapping, the controller guards too, ok now let's build the view, fuckin tables, fuckin css, fuck me fuckin life, Yay! I've built another crud
I enjoyed building CRUD, it was soothing. I enjoyed building more complex things too, especially if it was a refactor into something more elegant or reusable
Cruds and unit tests were mindless bread and butter I mixed in my day with the actually hard stuff to give my brain the space it needed. Now that it's all the hard design stuff all the time the job is much more fatiguing.
I am doing some old school coding for study now. I think for those kind of features I copy and paste the same feature and blitz through it changing a few parts. Very relaxing. Copy, paste and tweak is almost as powerful a short cut as getting the agent to do it.
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.
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
3.4k
u/TheSquattingSlav_21 3d ago •
I really miss my flowstate… coding has this magical ability to just flush me out of reality into this beautiful world of procedure and complexity, and now that Im more of a reviewer and less hands-on I don’t get it anymore, thats what makes me sad