NinetyNine
Joined 16 years ago
Joined 16 years ago
There are a few things you can try. You can create a personal project to explore the depths of "not refactoring", in hopes that you'll get used to it. You could also just try getting faster at your newer technique: writing code and refactoring in an hour instead of 3 (learning your tools like a master helps with this).
Your "sudden change" probably wasn't so sudden, but rather your experience with hitting the limitations of writing shitty code. Now you want to avoid those pitfalls in the future, but your boss doesn't seem to understand.
There's also plenty of places for you to go still, if none of the above works for you.
Edit: Creating a checklist of "the smallest chunk of work" can help you keep moving rather than getting stuck in tweakfinity.
You might want to speak to your manager next time something like that is happening, because there's no way it can be good for your productivity or the other people on your team. It's certainly not a normal practice. At the very worst, if someone isn't pulling their weight they should be dealt with in private.