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

[...]

- mike@mountaingoatsoftware.com

As useful as user stories can be, they’ve never been right for every team. An exciting alternative f [...]

- mike@mountaingoatsoftware.com

Being a great product owner is hard. Here are the things your team wants from you to help them do th [...]

- mike@mountaingoatsoftware.com

Want to learn about Kanban? Here’s a complete guide to introducing Kanban into your organization. [...]

- mike@mountaingoatsoftware.com

Lack of communication is a common problem that causes delays, rework, or adds risk. See how Kanban “ [...]

- Scott Hanselman

Jupyter Notebooks has been the significant player in the interactive development space for many year [...]

- Scott Hanselman

Visual Studio Online was announced in preview, so I wanted to try it out. I already dig the Visual S [...]

- Scott Hanselman

I'm an unabashed Adafruit fan and I often talking about them because I'm always making coo [...]

- Scott Hanselman

I was talking to Tara and we were marveling that in in 1997 15% of Americans had Passports. However, [...]

- Scott Hanselman

I've blogged at length about the great open source project called "Polly" NuGet Packa [...]

Meta