Comment by codelikeawolf

I spent about 9 years in web/frontend development and when all the AI coding things started coming out, I was admittedly concerned and defensive. I thought the output was gross, it couldn't help me with what I was working on, etc. I recently switched over to the backend, so now I'm dealing with an entirely different set of technologies, architecture, and problems to solve. I've found that, so far, about 80% of my time is spent planning, discussing requirements, determining how to integrate new features into the system or how fixing a bug may affect something else, etc. I use AI for the coding part because the code is sort of an afterthought. I've fully leaned into it and the experience has been fantastic. I ask Claude Code questions and bounce ideas off it. I ask it to write some code for me and I review it and make minor adjustments. The TLDR is I'm not really worried about it taking my job anymore, but I recognize that _not_ using it is going to become very obvious in the near future (it already is). This article pretty much nailed it. Engineering isn't just about pumping out lines of code, the code is just the output of your skills which provide the most value. Once I started looking at things that way, my stress level dropped considerably.