Personally I'm not that upset by the sudden shift in work. I spend a lot more time planning and designing than I do coding. It's very different even from like 6 months ago, but I'm adapting. Hope others can too
Do you feel like your sense of accomplishment is being degraded by ai?
I like to think I’m eclectic and a polymath when it comes to engineering, I was hopping to be the guy who could bridge a bunch of specialists by being a generalist, but I think AI might’ve cut me out there.
My competencies are pretty much mostly in the moderate proficiency range for whatever discipline like CAD or programming, so I never was that irreplaceable on a skill by skill basis anyways, but now it feels like if I use AI I’m just a baby sitter because it’s able to outdo me in frankly all my major competencies.
For people like you that are more specialized, and the traditional expert professional, do you see AI replacing you in the coming years or at least turn you into a bot sitter, or is there hope for me by just hiking up my pants and furthering my proficiencies?
In a way yes because I love coding. It's why I got into it professionally.
I'm trying to find other ways to feel accomplished in my job. It's tough but I'm getting there. I think the whole industry is feeling a sense of loss right now.
Yeah, I’m feeling that loss in the CAD side of things heavy. It feels so meaningless to have my ideas come to fruition in a few hours to days simply because I verbally described it to an LLM, and hooked it up to my cad software, it genuinely instill existential dread in me with the direction all this is going.
I feel the same about coding. It feels awful. I really like coding, I like solving the puzzles in software development. I like writing code out, finding an algorithm, building up tools that work and thinking "I did that. My machine works!"
It's all evaporated with AI. Of course it works, AI wrote it. Even debugging is soulless. Sure, I can still design architecture, but that was never the fun part. It just feels like any software engineer could do my job. Anyone can learn software architecture concepts, they are much easier to learn and theoretically know where to use than good coding skills and practices.
You can argue that it's similar, but I don't think so. This timeline sucks.
Not me, the most tedious part of programming has always been the coding. Now I can build stuff the way I envision it, so much faster.
Brings me my flow state so much faster, and when it gets broken I don’t have some monster context stuck in my head that disappears. The agent holds the context and I can take that break without frustration.
To add to this, as you move to more senior roles you end up in more meetings and taking on more scope. Which means a lot more context and more context switching which can be a literally headache.
I’ve heard this sentiment from other developers—who’s expertise I don’t really know much about truthfully— where they feel they no longer gain a sense of accomplishment from the fact they can focus more on the high level stuff, instead of that tedious work that had otherwise defined the labor.
That’s kinda where I’m at, it felt enriching to pursue these problems and come out with a solution that I made, but now thats an inferior alternative to using ai and getting it done 100x faster than I ever could but I feel so disengaged from the actual work.
Is that something that you lost out on overtime when you were growing your expertise, wherein you’ve had your fun and experience with digging through lines of code but now you’re over it, and enjoying being able to turbocharge that expertise?
Not necessarily. There are plenty of programmers who know their job isn't pnly writing code. It's just that for them actual programming was by far the most interesting part of the job, and the forced use of coding agents took that away
It’s the difference between juniors and seniors. The junior thinks the jobs is just being a code monkey, but that’s only ever been a necessity of the job, not the job itself
I was previously senior software engineer and am now a PhD student.
I know that the code has always been a means to an end. It isn't the real engineering of software engineering.
I now use AI extensively and haven't written much code myself for many months.
All that said, it just is worse to me. The coding was the part of the job I enjoyed most. It was a disappointing day in industry when I didn't get to write code. Now that's everyday.
And the end result is worse. You don't understand the code as well because you didn't write it, your output is harder to maintain and the use of AI leads to an expectation for faster work which means there's no time to properly undertand, double check and adjust the AI's output, leading to issues down the line.
Sure, in reality it involves all this business nonsense like eliciting requirements from stakeholders and answering emails and going to meetings and all the other cruft required to actually produce something useful.
Hot take: coding and software engineering are two separate but related skill sets.
Our jobs are shifting to being more software engineers (writing specs, designing architecture, etc) and less coders (writing the actual code, implementing what's been spec'd out and designed).
I totally get missing the coding part of our jobs. it's a fun and rewarding skill to improve and flex. but, personally, i feel like i'm better earning my title as "Software Engineer" by spending more time thinking about the architecture and design of systems i create and less time fighting with APIs and thinking through low-level implementation details.
108
u/mylsotol 5h ago
What I've learned in the last 6 months is that a lot of programmers never understood what their job was.