4 ms·
> The thing about bad technical decisions is that you can always undo them. Yes, it can be very frustrating, and obviously there’s all the wasted time and effo
by e19293001 11y ago
> The thing about bad technical decisions is that you can always undo them. Yes, it can be very frustrating, and obviously there’s all the wasted time and effort, but at the same time even that is not usually really wasted in the end
This words inspired me more as this has similar context as what Donald Knuth had said in his book The Art of Computer Programming[0]:
> At this point, it is often a good idea to scrap everything and start over again at step 1, or even at step 0! This is not intended to be facetious remark; the time spent in getting this far has not been wasted, for we have learned a great deal about the problem. With hindsight, we will probably have discovered several improvements that could be made to the program's overall organization.
[0] - http://www.amazon.com/The-Computer-Programming-Volume-Fascicle/dp/0201853922 http://www.amazon.com/The-Computer-Programming-Volume-Fascic... (Chapter 1.4.1 page 64)
- digi_owl 11y agoEven a negative result is data?
- munificent 11y agoI'm also a big fan of Fred Brooks' "The management question, therefore, is not whether to build a pilot system and throw it away. You will do that. […] Hence plan to throw one away; you will, anyhow." https://en.wikiquote.org/wiki/Fred_Brooks https://en.wikiquote.org/wiki/Fred_Brooks http://c2.com/cgi/wiki?PlanToThrowOneAway http://c2.com/cgi/wiki?PlanToThrowOneAway