3 ms·
I do not know the answer to your question, since for me programming has become a lot more enjoyable being able to throw outputs of LLM's together and then being
by fbrncci 3y ago
I do not know the answer to your question, since for me programming has become a lot more enjoyable being able to throw outputs of LLM's together and then being the glue in between with my expertise. Coming from my perspective, going back would throw me into a career with prospects which I started to lose passion for. Doing the same thing over and over again, spending weeks on stuff I have already solved many times over in different flavors, frameworks and languages.
I understand that some engineers/developers struggle with this change, but it also seems to be a personal take on ground breaking changes which are shaking up this career path; which are positive for some, and negative for others. Maybe we are on two different part of the spectrum, because I can't wait to have my job reduced to prompting and building even bigger things. IF it was not that way, I would have been close to a career change. No doubt, these changes will introduce new engineering challenges, which will be equally as exciting and in need of an engineering mindset as the previous paradigms have been.
- JohnFen 3y ago> I understand that some engineers/developers struggle with this change This isn't an issue of struggling with adapting to change. If it were just a matter of doing my job in a different way, that would be totally fine. This is an issue of seeing the sort of work that I enjoy -- the entire thing that drew me to this career -- evaporate completely. But this all makes me sound more upset than I actually am. I'm very troubled, but I also only have a decade or two left in my career, so I think it's likely that I'll be able to find niche positions where I can keep doing what I love to do. I do worry about younger devs who are in the business for similar reasons as me, though.