I agree with Michael Kennedy when he says that Software Development could be modeled as a Knowledge Discovery Process, “the process of going from 0% knowledge about an idea to 100% knowledge of a finished product ready for delivery to a customer“.
I agree so much that I decided to adapt my future Daily Scrums to this.
Well, if only I had seen then what I saw today, I would have used in my talk, since I think it would have been the perfect example.
See what I found in a recent production code.
Right now, it hangs on the wall of our open space, for all the developers to see.
Rule #1: write commit comments before coding
Rule #2: write what the software should be supposed to do, not what you did
I wasn’t able to be concise enough. Since Susana’s question made me think of three other questions which I do not know the answers, I’m sharing them with you all.
Find here the follow-up of this post.
I find it vaguely irritating when the abused image in which software is described as an intangible product is used.
Software is, of course, intangible as of dictionary definition (“Incapable of being perceived by the senses, Incorporeal“) since it’s made of bits and bits obviously cannot be touched.
But this is not the abuse I’m talking about. The annoying cliché used in tons of posts and articles speciously refers to another meaning, and it’s very often used by-end.