3 ms·
I don't think the author's skills were atrophying, but they may have been stuck at a certain level. I have Thoughts about that. On the one side: I get it. As a
by Cthulhu_ 5y ago
I don't think the author's skills were atrophying, but they may have been stuck at a certain level. I have Thoughts about that.
On the one side: I get it. As a developer you want to - and the industry expect you to - keep learning, always be on the increase, etc.
But on the other hand, when you think about it, once the main architecture is put down and the main issues are solved, most software engineering jobs are just repeating the same trick over and over again, copy / paste / edit some names, done.
The last part is where you want to end up at as a company, basically; build features end to end in a reasonable time. But it's not what most developers want, they want new challenges, they want to stay in the problem solving domain.
I think as a developer you need to accept that a big chunk of your job, and what your employer wants you to do, is kinda boring. It's not solving new problems, it's extending the functionality of an application using existing solutions.
And if you're hired as a front-end developer or whatever, the hiring company may not want you for what you can become, but what you already are.
And honestly, just trying to find decent developers that don't need to learn your stack is already difficult enough.
- WastingMyTime89 5y ago> But on the other hand, when you think about it, once the main architecture is put down and the main issues are solved, most software engineering jobs are just repeating the same trick over and over again, copy / paste / edit some names, done. I don't know. I think it gets less and less true as you get away from web development. The fundamentals stay the same but how they intersect with what you are doing can vary widely. If you want to, you can encounter domain knowledge intersecting with the problems you are trying to solve, different architectures for complexe systems coming with their own set of constraints, different project structures, different ways to deal with end users requirements. I think they are plenty of opportunities to do boring things and plenty to do interesting things.
- danjac 5y agoAnother problem is that developers will start pushing for solutions in their current job not because it makes sense but because they know they're going to need those skills in their resume in a year or two. The company is left with a React-sized hole (or k8s, or Vue, or whatever) when the developer moves on that they need to fill ASAP, and the cycle continues.
- worker767424 5y agoFunny enough, he was a little bitter about being down-leveled, but it looks like that was the right call.