3 ms·
It's interesting as analogies go, but the real problem is that eating is inevitable. You will eat eventually and consistently. But with code there is no guara
by dasil003 15y ago
It's interesting as analogies go, but the real problem is that eating is inevitable. You will eat eventually and consistently. But with code there is no guarantee you will ever ship. There are many programmers whose quest for perfection almost completely prevents shipping. On the other hand an obsession with eating the best food is not nearly so crippling; it is more unilaterally beneficial despite whatever flaws or inconveniences it may cause (road trips, wrong definition, etc).
- city41 15y agoI have found finding the balance between quality and actually shipping to be one of the most challenging aspects of being a good developer. Sometimes "good enough" really is, and other times it really isn't. Distinguishing between the two (and all the gray in between) takes experience.
- Retric 15y agoI think they are orthogonal issues. For any code base there are a list of things most in need of improvement and a quality threshold to be able to ship. It's all to easy to spend a lot of time making unimportant things better, but the problem is not trying to make great code it's working on the wrong area. If the messaging system sucks and there is no GUI then build a GUI.
- dasil003 15y agoIndeed. There are few things as satisfying in the craft of programming as discovering some code that you wrote years ago which foresaw conditions that didn't exist then but do now. Deleting ugly code which did the job but is now unnecessary is a close second.