Ask HN: Patterns for limiting the scope of your work? (as a junior dev)

Hi HN,

In all of my projects from school to work to personal, I tend to do a lot more work than required to achieve a quality that is not necessary.

For example, even though a script of mine might run only once or twice per year I spend a lot of time writing unit tests, properly structuring the code and refactoring for readability.

As a junior dev it's hard to figure out the quality-time tradeoffs that should be made as I want to create good quality code but I don't want to take significantly longer than others to complete it. How do you effectively limit the scope of your work?