With the exception of the first book, I've read them all. The strange thing is, I didn't learn a single thing from them. Has anyone else had similar experiences with these, or design books in general? They seem to either confirm the blatantly obvious, or state theories that you see problems with .5 seconds after reading them.
It seems to me a good design book would be 90% code. Perhaps I'll just go read the 2.4 kernel again (-;
| [reply] |
In many cases good design is obvious. The second part of good design is that sometimes you have to do something that isn't good design, and that is good design.
For every design rule there is an exception. The trick is to know when that exception is happening.
If you're finding you see problems with many things, perhaps you should point such things out to the author, or note them in your web journal, assuming you have one.
| [reply] |
perhaps you should point such things out to the author
I do, when they make themselves available through online discussion groups. Otherwise I don't bother them (how would you feel if you received 1000 emails telling you of the same questionable error?).
or note them in your web journal, assuming you have one.
I don't. If I ever do, please kick me off the Internet ;-)
The second part of good design is that sometimes you have to do something that isn't good design, and that is good design.
Putting aside logical fallacies ;-), I'd like to think otherwise. Since wanting to think otherwise hardly means its true, could you provide an example?
| [reply] |