3 ms·
You should at the very least be reading your own code. It's the feedback loop to improvement. >> " Coders don't need to develop an elaborate aesthetic sensiti
by bumblebird 17y ago
You should at the very least be reading your own code.
It's the feedback loop to improvement.
>> " Coders don't need to develop an elaborate aesthetic sensitivity to judge whether their work passes their goals - unit tests and benchmarks will do just fine."
If your goal is "It works", then sure. But some of us aspire to something more than that.
- mdemare 17y agoOf course you should read your own code. How can you not read your own code? This is about whether it makes sense to pick an open source project and start reading.
- bumblebird 17y agoYou'd be surprised. People using IDEs for a start, code folding, hiding from the cruft.
- biz2hack 17y agoHow are you supposed to know though, when your code is doing better then 'it works'?
- mbrubeck 17y agoIt's efficient. It's concise. It's easy for you to understand and modify. It's easy for others to understand and modify. Over the long term, it proves to have a low defect rate. It's declarative, and lends itself to automatic optimization.