MVC in "Head First Design Patterns" - I am confused.
in [OOP]
|
Prev: [ANN] Free Session: In-the-Brain of Martine Devos on Agile Estimation & Planning
Next: Modularity problems with multiple dispatch (was: Scala and problemswith OOP)
From: Michael Redlich on 11 Nov 2007 01:32 On Nov 10, 6:50 pm, topmind <topm...(a)technologist.com> wrote: > Michael Redlich wrote: > > On Nov 8, 4:27 pm, topmind <topm...(a)technologist.com> wrote: > > > Firkraag wrote: > > > > Hello > > > > > I've been reading "Head First Design Patterns". > > > > Burn it! That book is a piece of garbage. It teaches you to hard-wire > > > product classification into textual code. In practice, a store > > > administrator will need the ability to alter and manage product > > > classifications so that they don't have to call the programmer out of > > > bed Sunday at 7am. Usually such info would be in databases, or at > > > least config files. > > > > As a catalog of "toy examples" to illustrate OOP design patterns, it > > > may be fine. But as far as practicality, tie it to the pigeons and > > > fire a pistol into the air. > > > > -T- > > > ... people DO go out into the > real world and start writing code like that and make job-security > messes. I've dealt with maintaining a lot of bad programs written by > others that hard-wire stuff left and right. > > While I don't doubt that this is true, real developers should know better... > > My criticism is legitimate because excess hard-wiring is a real > problem. > > As small note after each major example about how it should really be > done is not asking too much. > I can see your point, but I still believe that examples should be as simple as possible to reinforce what is being taught. Mike.
From: topmind on 11 Nov 2007 02:51 Michael Redlich wrote: > On Nov 10, 6:50 pm, topmind <topm...(a)technologist.com> wrote: > > Michael Redlich wrote: > > > On Nov 8, 4:27 pm, topmind <topm...(a)technologist.com> wrote: > > > > Firkraag wrote: > > > > > Hello > > > > > > > I've been reading "Head First Design Patterns". > > > > > > Burn it! That book is a piece of garbage. It teaches you to hard-wire > > > > product classification into textual code. In practice, a store > > > > administrator will need the ability to alter and manage product > > > > classifications so that they don't have to call the programmer out of > > > > bed Sunday at 7am. Usually such info would be in databases, or at > > > > least config files. > > > > > > As a catalog of "toy examples" to illustrate OOP design patterns, it > > > > may be fine. But as far as practicality, tie it to the pigeons and > > > > fire a pistol into the air. > > > > > > -T- > > > > > > > ... people DO go out into the > > real world and start writing code like that and make job-security > > messes. I've dealt with maintaining a lot of bad programs written by > > others that hard-wire stuff left and right. > > > > > > While I don't doubt that this is true, real developers should know > better... Real developers are not going to buy a book with a sloppily-dressed attitude-dripping teenage girl with pigtails on the cover. What's next, "Learning OOP under Ecstasy"? > > > > > My criticism is legitimate because excess hard-wiring is a real > > problem. > > > > As small note after each major example about how it should really be > > done is not asking too much. > > > > I can see your point, but I still believe that examples should be as > simple as possible to reinforce what is being taught. A disclaimer only takes a paragraph or two. It is not an either-or choice. > > Mike. -T-
From: Michael Redlich on 13 Nov 2007 22:29 On Nov 11, 2:51 am, topmind <topm...(a)technologist.com> wrote: > > Real developers are not going to buy a book with a sloppily-dressed > attitude-dripping teenage girl with pigtails on the cover. What's > next, "Learning OOP under Ecstasy"? > Ah, but didn't you ever learn that you shouldn't judge a book by its cover??? Cheers... Mike.
From: topmind on 14 Nov 2007 14:04 Michael Redlich wrote: > On Nov 11, 2:51 am, topmind <topm...(a)technologist.com> wrote: > > > > > Real developers are not going to buy a book with a sloppily-dressed > > attitude-dripping teenage girl with pigtails on the cover. What's > > next, "Learning OOP under Ecstasy"? > > > > Ah, but didn't you ever learn that you shouldn't judge a book by its > cover??? Let me reword that: real developers would be embarrassed to purchase a book with that kind of cover (which is mirrored in the page photos also). It just looks newbie-ish. Maybe I'm just an old foggie who is not hip to the styles. > > Cheers... > > Mike. -T-
From: Michael Redlich on 15 Nov 2007 16:56
> > Let me reword that: real developers would be embarrassed to purchase a > book with that kind of cover (which is mirrored in the page photos > also). > > It just looks newbie-ish. Maybe I'm just an old foggie who is not hip > to the styles. > > I'm probably older than you, so I don't need to hear the old foggie bit. The Head First series of books explains concepts in a way that make you understand instead of remembering. There is an old saying: If you understand, you don't have to remember... Why don't you try reading the section of the book that explains their teaching paradigm instead of looking for a disclaimer about their examples... I suppose we can agree to disagree... Mike. |