Lovely, these advices worth a million. :) May I quote them in my blog?
Henry On Feb 21, 9:52 am, Jared Rypka-Hauer <[email protected]> wrote: > Henry, just for you and on the spur of the moment, I came up with > aphorisms for would-be OOers. It's interesting because I actually > before reading anyone else's advice and now I realize that they're > things others have said as well. That should give you some confidence > in the fact that, well, the basics are universal. > > And so, here we go, J's 10 Aphorisms for Would-Be OO Programmers: > > There's no perfect design, but there are seriously bad ones. > Any design that works is better than one that's very clever yet very > brittle. > You're better off with working code than no code (even spaghetti code). > You'll probably never understand a problem space till you've gotten it > all wrong at least once. > ( ^ That's why they say "we learn from our mistakes".) > Your initial idea is a starting place based on a limited understanding > of the domain. The rest we call "refactoring". > There is life beyond refactoring. It's called "Maintenance". > Version 1: Sorta. Version 2: Better!. Version 12: God, remember how > bad version 1 sucked? > Behind every successful programmer is a huge library of books he > hasn't looked at in years. > Everything you ever learn is only a theory till you learn it for > yourself (usually the hard way). > > HTH! > > On Feb 20, 2009, at 6:16 PM 2/20/09, Marc Esher wrote: > > > Henry, permit me to add to the list of "Things Henry Ought To Do To > > Learn Himself Some OO". ... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
