4 ms·
I don't think that counts. I love code but code doesn't capture the "whys". It's also not very good at giving an overview of the problem.
by 8n4vidtmkvmk 4y ago
I don't think that counts. I love code but code doesn't capture the "whys". It's also not very good at giving an overview of the problem.
- mixedCase 4y agoThe "why" is pretty much the only reason to write comments! Overviews of the problem are more in the realm of spec rather than implementation planning and is another issue altogether. Of course you need to know what you're solving, but it is my point that I don't need to write a detailed document on how I'm going to solve most everyday problems when I can jump into the code and progressively work from there using the tools provided by the language.
- 8n4vidtmkvmk 4y agoMost everyday problems don't need a doc to explain what you're going to do. At my work though, if you're going to adopt a major framework or service, you need a doc explaining why you chose that one. It's a big decision that will last years.