There are numerous ways to find satisfaction in work. I'd merely extend the reasons you list to include an enjoyment of the tooling and software you're working with. Might as well try to tick all the boxes.
There are numerous ways to find satisfaction in work. I'd merely extend the reasons you list to include an enjoyment of the tooling and software you're working with. Might as well try to tick all the boxes.
For work projects you can't just join a team and ask let's rewrite it in X. Some developers will try to get satisfaction with the latest and greatest but this is a moving target, a few years back C# was cool, then it was cool to know Scala because is functional, now is cool to uise Rust, GO or some compile to JS and react or similar frameworks, when this are no longer cool this developers leave and somebody else will have to take over and meintein their amateur code (by definition you can't be experienced in new thing since is new)
Anyway I got off-topic, my point is that refactoring your personal project is not the same as refactoring. cleaning up a big old project(in my case 4 year old angular1 project , that probably has a few deprecated dependencies that are no longer cool enough). It would be better a bit to work with a better code in TypeScript and latest React but I personally won't hunt for a new job because of the tools.