I don't write code anymore. So what do I actually do and where's the fun?
Work as I knew it changed completely for me this year. All those frameworks, languages and libraries I've learned and used over the past years combined are not even close to the scale of change in how I work as a software developer. I always worked within small teams, which meant being very practical, writing lot of code. And I loved it. I enjoyed rearranging the characters, making the code more…
This year marked a significant shift in the author's role as a software developer. Gone are the days of writing extensive code, as the use of frameworks, languages, and libraries has drastically changed the nature of their work. The author once thrived on the challenge of rearranging code and making it more coherent, but now their daily tasks involve creating specifications, defining test scenarios, and ensuring they are implemented correctly using AI.
This change has led to a reduction in manual coding and an increase in testing and data preparation. The author has even taken on solo projects outside of work, finding immense satisfaction in completing them within a short time frame. However, this newfound efficiency comes with its own set of challenges. The rapid pace of AI-related developments can feel overwhelming, and the lack of established guidelines for integrating AI into workflows is causing bottlenecks and potential burnout.
The author stresses that while the job has changed, it's not necessarily a tragedy, and adaptation is key to thriving in this new environment.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
