What comes to mind is Niklaus Wirth's programming language Modula 2. He first wrote it, threw it away, and then wrote it again - on purpose. I seem to recall he wrote something like he never got it right the first time so he just decided he would write it twice to begin with. I am also an OCD planner type, but have managed to "just do it" while also planning to likely toss whatever comes out and start over. It's always so much easier the second time.
Yeah, there's a lot of things where you just can't mentally imagine all the pitfalls and edge cases until you sit down and build something once to work out the details... deciding to do it twice ahead of time is a great trick that I should try
I remember hearing that approach recommended by someone who was working on scientific software - do it once to figure out what the problem looks like, and then redo it so you can make the architecture work.
What comes to mind is Niklaus Wirth's programming language Modula 2. He first wrote it, threw it away, and then wrote it again - on purpose. I seem to recall he wrote something like he never got it right the first time so he just decided he would write it twice to begin with. I am also an OCD planner type, but have managed to "just do it" while also planning to likely toss whatever comes out and start over. It's always so much easier the second time.
Yeah, there's a lot of things where you just can't mentally imagine all the pitfalls and edge cases until you sit down and build something once to work out the details... deciding to do it twice ahead of time is a great trick that I should try
I remember hearing that approach recommended by someone who was working on scientific software - do it once to figure out what the problem looks like, and then redo it so you can make the architecture work.