Bad documentation is bad documentation whether it's in a picture or in text.
I have found that most software engineers get so hung up on UML notation of their diagrams that they end up never doing any because it takes too much effort.
Start with simply and succintly writing what the software does COMPLEMENTED by a diagram. Not the other way around.
Diagrams on their own are useless without some accompanying explanation. Ever read a book full of diagrams?
Today's user wants to grab just about anything and not worry about installing it and making it work
He seems to imply that we're being greedy wishing for this? What a strange comment to make. Of course this is what people want! And it should be this easy under Linux too...
Even Zawinski agrees: http://www.livejournal.com/users/jwz/302761.html?n c=4
Slashdot Mirror
Wow. It scares me that you know all of that.
Bad documentation is bad documentation whether it's in a picture or in text.
I have found that most software engineers get so hung up on UML notation of their diagrams that they end up never doing any because it takes too much effort.
Start with simply and succintly writing what the software does COMPLEMENTED by a diagram. Not the other way around.
Diagrams on their own are useless without some accompanying explanation. Ever read a book full of diagrams?
He seems to imply that we're being greedy wishing for this? What a strange comment to make. Of course this is what people want! And it should be this easy under Linux too...
Even Zawinski agrees: http://www.livejournal.com/users/jwz/302761.html?n c=4