The SOLID principles of object-oriented design
en.wikipedia.org
The SOLID principles of object-oriented design
1–10 of 21 posts
Re: The SOLID principles of object-oriented design
#2" It is typically used with test-driven development".
Talk about creating confusion in the mind of the reader. They might have applied some of the sold principles to this article and separated out this completely orthogonal concern. This is what annoys me about Wikipedia sometimes. It's full of "editors" hijacking articles to propagate their manifesto of the week instead of just sticking to the subject.
Re: The SOLID principles of object-oriented design
#3There is a fantastic talk by Kevlin Henney where he deconstructs the SOLID principles as each being either misunderstood when they were written - or frequently misunderstood after. It was done here:
http://scottishdevelopers.com/tag/solid/
http://sydney.yowconference.com.au/
I won't spoil it by writing all the points here - just some pearls.
* The Open/Closed principle is redundant because it is already covered by the Liskov substitution principle.
* Bob Martin's view of the Dependency Inversion principle is in fact the Single Responsibility principle.
He suggests 5 more principles - but I won't spoil it by listing them here. Go see it!
Re: The SOLID principles of object-oriented design
#4" It is typically used with test-driven development". Talk about creating confusion in the mind of the reader. They might have applied some of the sold principles to this article and separated out this completely orthogonal concern. This is what annoys me about Wikipedia sometimes. It's full of "editors" hijacking articles to propagate their manifesto of the week instead of just sticking to the subject.
If only there were some way to rectify these issues
Re: The SOLID principles of object-oriented design
#5There is a fantastic talk by Kevlin Henney where he deconstructs the SOLID principles as each being either misunderstood when they were written - or frequently misunderstood after. It was done here: http://scottishdevelopers.com/tag/solid/ http://sydney.yowconference.com.au/ I won't spoil it by writing all the points here - just some pearls. * The Open/Closed principle is redundant because it is already covered by th…
Is there a video of the talk? I can't find it.
Re: The SOLID principles of object-oriented design
#6There is a fantastic talk by Kevlin Henney where he deconstructs the SOLID principles as each being either misunderstood when they were written - or frequently misunderstood after. It was done here: http://scottishdevelopers.com/tag/solid/ http://sydney.yowconference.com.au/ I won't spoil it by writing all the points here - just some pearls. * The Open/Closed principle is redundant because it is already covered by th…
Is there a video of the talk? I can't find it.
No, I don't really understand the parent link as you can't get a transcript or video. I was at the talk in Scotland though, and it was very good.
I recently asked Kevlin if a version would be made available - this was his reply:
"Not yet. I'm doing a version of it at @yow_oz next month. I think they'll be recording it — last year's talks went up quickly." https://twitter.com/KevlinHenney/status/402743019956604928
The conference has just finished, and the website where the talks will go up seems to be here: http://yowconference.com.au/
Re: The SOLID principles of object-oriented design
#7" It is typically used with test-driven development". Talk about creating confusion in the mind of the reader. They might have applied some of the sold principles to this article and separated out this completely orthogonal concern. This is what annoys me about Wikipedia sometimes. It's full of "editors" hijacking articles to propagate their manifesto of the week instead of just sticking to the subject.
If only there were some way to rectify these issues
If that was sarcasm directed at him with the implication that he should try to fix it by editing it himself, I'm not sure how much experience you've had trying to edit a Wikipedia article. It can be a horrid experience.
Re: The SOLID principles of object-oriented design
#8Useful article but too small content for this important theme.
Re: The SOLID principles of object-oriented design
#9Earlier quoted context omitted.
If only there were some way to rectify these issues
If that was sarcasm directed at him with the implication that he should try to fix it by editing it himself, I'm not sure how much experience you've had trying to edit a Wikipedia article. It can be a horrid experience.
Edited.
Re: The SOLID principles of object-oriented design
#10A lot of programmers don't like/know/care about SOLID or good code design/architecture and also end up complaining when their codebase is a big, huge mess. Often times, just following good OOP principles (and some FP principles) makes it easy to clean up most messes.
The biggest thing I think many programmers suffer from is wanting to have too few objects with big, ugly methods inside.
More objects, fewer methods, smaller methods is often the answer to managing complexity, but it seems like humans don't like appropriately recognizing the complexity of the problems they are working with, even when confronted with the mess they make to solve them.