Use the 80:20 rule (Pareto Principal) And a "TODO" notation.

Or, as given here, "80% of the task is completed by 20% coding".

A large amount, ~80% of your code, can probably be written cleanly, and quickly. Do that. Say you need to add functionality, and a class or module already exists for it. Just add it to the obvious place. Follow the existing naming conventions. Add basic unit tests. Build on what's already there.

~20% of your code requires more thought. You aren't sure how to test some obscure edge case. You can't decide about the added functionality - should it be in a subclass, or use D.I., or some fancy Gang of Four pattern. (etc...) As your mind wanders you start to research a new tech buzzword and spend hours on Stack Overflow.

STOP.

1. Just do something quick and dirty.
2. And a TODO comment.
3. Come back to it in a couple of days.

It's amazing how a few days of background thought can clarify a vexing problem. Chances are, you have figured out a better, cleaner way to do it. If you haven't, that's when you engage the help of a fellow programmer, a mentor, or you bring it up at the standup, code review, etc.

p.s. If only 20% of your coding is "easy", then you or your code base have a problem...

Use the 80:20 rule (Pareto Principle) And a "TODO" notation.

Or, as given here, "80% of the task is completed by 20% coding".

A large amount, ~80% of your code, can probably be written cleanly, and quickly. Do that. Say you need to add functionality, and a class or module already exists for it. Just add it to the obvious place. Follow the existing naming conventions. Add basic unit tests. Build on what's already there.

~20% of your code requires more thought. You aren't sure how to test some obscure edge case. You can't decide about the added functionality - should it be in a subclass, or use D.I., or some fancy Gang of Four pattern. (etc...) As your mind wanders you start to research a new tech buzzword and spend hours on Stack Overflow.

STOP.

1. Just do something quick and dirty.
2. And a TODO comment.
3. Come back to it in a couple of days.

It's amazing how a few days of background thought can clarify a vexing problem. Chances are, you have figured out a better, cleaner way to do it. If you haven't, that's when you engage the help of a fellow programmer, a mentor, or you bring it up at the standup, code review, etc.

p.s. If only 20% of your coding is "easy", then you or your code base have a problem...