OO Principles

[jdpjamesp]

Can any of you brainboxes point me in the direction of a high(ish) level resource explaining basic OO principles? I learnt it all at uni but things have moved on a lot since then and I've forgotten it all as well

 

[tamhas]

Well, for quick and dirty there is http://cintegrity.com/content/Basic-Concepts
But, if you want more serious education, I would go for Model-Based Development by H.S. Lahman http://cintegrity.com/Lahman While you might think the title is pointing in a direction which may not interest you, the way Lahman does MBD, it is the best schooling on OO that I know of.

 

[jdpjamesp]

Thanks Thomas. That white paper looks a good place to start. I don't have time to get into too much detail just now, but I'll file the Lahman away for a rainy day

 

[jdpjamesp]

Actually Lahman has Agile in the title which might actually be spot on for what I'm looking for

 

[tamhas]

Maybe a rainy week ... but it is possible to read it in pieces. It makes better reading than most things of the sort.

 

[tamhas]

You mean the Lahman whitepaper? Nice little piece. I point to it frequently.

 

[Joe Meyer]

Another frequent term linked with Object Oriented Programming is SOLID programming. Also if you look poke around long enough you can find that Robert Martin (AKA Uncle Bob) is kind of the authority on these principles. Be sure to check out youtube for some of his talks, I'm sure you'll find entertaining if not enlightening.

 

[GregTomkins]

Robert Martin 'Clean Code' = one of my favorite programming books. IIRC it was more about naming and comments than SOLID though. Martin Fowler is another interesting one, though he covers a huge range of business programming topics, OO technique is just a tiny part.

 

[Joe Meyer]

Robert Martin 'Clean Code' = one of my favorite programming books. IIRC it was more about naming and comments than SOLID though. Martin Fowler is another interesting one, though he covers a huge range of business programming topics, OO technique is just a tiny part.

I'd agree that is has quite a bit to do with naming and comments, but it also touches on things like DRY principle, having minimal dependencies, and extendibility (if that's even a word?); which I do think are things that good OO design need to incorporate. Regardless it's good info.