Object Orientated Design and SOLID Principles – Dot Net Curry

Home » Software Architecture and Design » Object Orientated Design and SOLID Principles – Dot Net Curry
Photograph of columns in old building

I read DOT NET Curry on a regular basis. One of the things that I think is really important to understand is object orientated design and the SOLID principles originally documented by Uncle Bob Martin.

I’m not going to repeat what has been said by others, this blog will focus on some (hopefully) well thought out examples, but this post links to some of the resources I have found interesting. There is a wealth of information on DOT NET Curry.

Why should you care about SOLID principles? Isn’t it just something else to remember? The main thing in my mind is that it changes your way of thinking away from the existing code into more about what the code should be doing. Also having more objects, but better named, shorter and simpler with less dependencies really is a breath of fresh air – it makes a system really reliable and easy to maintain if you can read the code. In my view, all developers should study SOLID principles to understand just how readable your code could be, before you decide if you should use this or not. Code readability, whatever methods you use, is very important. If your code is readable enough, you can spot many of your remaining bugs just by reading it.

For those new to object orientated design, I highly recommend Head First Object Orientated Analysis and Design on my Software Architecture and Design Books page.

About Phil

I have been working as a software developer since 1983. This blog could have been called "From Fortran 77, C and Cobol to C# in 20 (not so) easy years", but it doesn't sound quite right somehow. Besides I'm talking about what's happened since 2003, not before!
One Response to “Object Orientated Design and SOLID Principles – Dot Net Curry”
  • preetiagarwal

    Thanks for sharing articles related to ASP .NET, in the recent time lot of online business have started migrating to ASP. The reason behind migration is that it allows developers to develop more reliable, scalable and secure software.

    Reply

Leave a Reply

Your email address will not be published.


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">




Top Posts & Pages

Categories

Recent Posts

Recent Comments

Archives

Blogroll

  • Mike Cohn's Blog
  • Scott Hanselman's Blog
- mike@mountaingoatsoftware.com

From helping teams understand the boundaries of self organization to creating safety around things l [...]

- mike@mountaingoatsoftware.com

Your team is probably spending too much time in sprint planning meetings. Here’s how to spend less t [...]

- mike@mountaingoatsoftware.com

Debating between Scrum and Kanban? Guest author Brendan Wovchko offers five advantages Kanban has ov [...]

- mike@mountaingoatsoftware.com

Most individuals know that multitasking slows us down. It has an equally negative effect on agile or [...]

- mike@mountaingoatsoftware.com

Announcing the world’s only dating website for Scrum Masters and product owners. [...]

- Scott Hanselman

I think that we, as an industry, are still figuring game streaming out. It's challenging to fin [...]

- Scott Hanselman

If you find yourself learning C# and .NET and come upon the "Run your first C# Program" do [...]

- Scott Hanselman

I was at the Microsoft BUILD conference last week and spent some time with a young university studen [...]

- Scott Hanselman

I've blogged before about the Azure Cloud Shell. It's super cool and you can get your own [...]

- Scott Hanselman

"My fellow Windows users, our long national nightmare is over." The Windows Terminal is he [...]

Meta