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

If you’ve estimated with Planning Poker, you may very well have used cards with either the FIbonacci [...]

- mike@mountaingoatsoftware.com

For many teams, the sprint review has run its course and it’s time to stop doing them. Blasphemy? Ma [...]

- mike@mountaingoatsoftware.com

In an ideal world, a Scrum team could perform the work of its sprints entirely uninterrupted. Produc [...]

- mike@mountaingoatsoftware.com

Do Scrum long enough and someone will suggest stopping the daily scrums. Here’s how to reply. [...]

- mike@mountaingoatsoftware.com

When estimating in story points, teams should think in terms of ranges and rounding up. Here’s why. [...]

- Scott Hanselman

Microsoft released a nice new ligature-friendly open source font this week called Cascadia Code. It [...]

- Scott Hanselman

I was reading an older post in an emulator forum where someone was asking for a Playstation 1 (PSX) [...]

- Scott Hanselman

I'm pretty happy with Windows 10 as my primary development box. It can do most anything I want, [...]

- Scott Hanselman

It's early days (preview) but there's now a Terminal integrated into Visual Studio! Taking [...]

- Scott Hanselman

Yesterday the Windows Team announced the first preview and code release of PowerToys for Windows 10. [...]

Meta