I've found that there are a few delaying tactics and strategies that help by simply postponing writing code. Test Driven Development and Behavior Driven Develo

I've found that there are a few delaying tactics and strategies that help by simply postponing writing code. Test Driven Development and Behavior Driven Development (TDD/BDD) are probably the most widely used, and a relatively easy sell to other members of your team, but when your brain is really boiling over it may not be enough to keep you from writing tests that are too specific to the implementation you have in mind. If that's the case, it can help to take a further step back and start by writing DocTests where the motivating narrative is interleaved with a basic exercise of the code as it is intended to be used (additional unit and integration tests are later added to cover corner cases that aren't part of the main narrative). This can productively be pushed further into an actual Documentation Driven Development process, especially if the code in question is intended to be used by external technical stakeholders. Literate Programming (where a narrative and implementation are intertwined, rather than a narrative and tests) can also resemble this sort of process, but support in toolchains is uncommon.