3 ms·
Personally, I'm suspicious of anyone who doesn't document what they did. If you are unable to take the time to leave a trail of your thought processes and reaso
by angstrom 19y ago
Personally, I'm suspicious of anyone who doesn't document what they did. If you are unable to take the time to leave a trail of your thought processes and reasons then the understanding you claim to have about your domain is suspect. The only exception is if it's throw away code.
- Hexstream 19y agoMost of my code is "throw-away" code :| In the sense that even if it's about the best code I can produce right now, in a couple months I'll have learned so much and improved the rest of the system incrementally so much that my formerly-best code I will need to throw away (as in refactor or even rewrite).
- phaedrus 19y agoDocument it anyway! Although it might seem like a waste of time to write about something that will change, the fact is that all software is potentially throw-away code. That's the "soft" in software - you can and should change it if it needs to change. If didn't document things that might change, you'll either never document or you will be loathe to change code that has been documented. Instead, just look at both the code and the documentation as a working sketch.