interesting thing about losing 4 hours of code is that it should only take about 20 minutes to rewrite it again.
most of coding is not about just typing, its figuring out a large puzzle. once you know the solution to the puzzle you can just write down the solution again from memory.
It’s always better the second time despite the annoyance
There’s a lesson in there
That would be an interesting approach for a machine learning algorithm
80/20
I bet the state of being annoyed over losing 4 hours of work took more than 20 min. 😉
It’s a long 20 minutes though
Same with design. You could spend 8 hours messing with pixels and not have anything solid, take a nap, and work it out in 10 minutes.
This is why I just take a break if I’m stuck. No point in wasting time.
Funny how that works.
yeaaaa
This is very true of financial modeling as well
The second time round you might find yourself doing even a better job.
Nice.
and sometimes improve the solution
especially if you thought hard about it, and hopefully scribbled something on paper all along
typing is not the bottleneck
and usually the 2nd one is better
