We've been told all our life to NEVER procrastinate. I think that's wrong. Sometimes, procrastinating is exactly what we should be doing. A few thoughts below. Unless it's something very very very very small, take as much time as you need to: think about the issue, and its importance understand the problem weigh PROs and CONs tinker with the code or the problem, throwing the solution away at the end evaluate impact outside our project: is it going to make things better for us, but worse for somebody else (i.e. optimize globally) find out how others have solved the same problem: it's very likely we're not quite the only ones working on this problem. How have others solved it? avoit NIH (not invented here) As a developer, you can do all of the above when you open the github (if you use github) issue: spend as much time as needed to clearly explain what is going on, and try to answer as many as possible of the questions above. Only after you are ready, start (and finis
Delivering the improbable.