Home » Software Architecture

Single Responsibility SOLID Principle

18 September 2012 No Comment

Let’s do a deep dive into the first of the SOLID principles for good object oriented software design. What is a responsibility? Why should it be single? How do we make it single? We’ll examine all these issues in extreme detail. We’ll look at some old code to see whether it conforms or not. We’ll also look at various design patterns and strategies that help us conform to this principle.

Video Producer: http://www.ndcoslo.com/

Related Videos:

Comments:

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Be nice. Keep it clean. Stay on topic. No spam.

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

This is a Gravatar-enabled weblog. To get your own globally-recognized-avatar, please register at Gravatar.

*