I have noticed that there are generally three kinds of software releases.
1. No code, just vaporware.
2. Some code, no to few tests, very little documentation.
3. Well written code, lots of tests, lots of documentation.
The first is annoying. The second sometimes contains interesting snippets if you're willing to dig. I read the code but am unlikely to use it. The last kind, when I find it, is gold. I use it, read the code, and refer back to it.
I have a theory that these kinds of code correspond to intent. Some people want to get something out (sometimes just words) and others want to provide something useful.
My zen koan is: if it were not for the chaff, you might not have wheat.
Comments
I have noticed that there are generally three kinds of software releases.
1. No code, just vaporware.
2. Some code, no to few tests, very little documentation.
3. Well written code, lots of tests, lots of documentation.
The first is annoying. The second sometimes contains interesting snippets if you're willing to dig. I read the code but am unlikely to use it. The last kind, when I find it, is gold. I use it, read the code, and refer back to it.
I have a theory that these kinds of code correspond to intent. Some people want to get something out (sometimes just words) and others want to provide something useful.
My zen koan is: if it were not for the chaff, you might not have wheat.