Comments on: Design principles http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/ A night's vision on .NET Sat, 17 Oct 2009 11:00:07 +0200 http://wordpress.org/?v=2.8.4 hourly 1 By: fuzzelogic http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-3596 fuzzelogic Fri, 03 Jul 2009 15:21:06 +0000 http://www.noctovis.net/blog/?p=66#comment-3596 Hi! Just found your blog. Pretty nice principles. I've blogged about the similar principles (http://fuzzelogicsolutions.com/wordpress/index.php/2009/04/16/object-oriented-design-principles/). In my post I hinted at a challenge to maintaining LoD while using DDD. LoD (via an example) states don't do the following. var payment = Client.Wallet.GetMoney(200.00); But DDD states you should Traverse your aggragates. Do you have any thoughts on this. Thanx Hi! Just found your blog. Pretty nice principles. I’ve blogged about the similar principles (http://fuzzelogicsolutions.com/wordpress/index.php/2009/04/16/object-oriented-design-principles/). In my post I hinted at a challenge to maintaining LoD while using DDD.
LoD (via an example) states don’t do the following. var payment = Client.Wallet.GetMoney(200.00);
But DDD states you should Traverse your aggragates.
Do you have any thoughts on this.
Thanx

]]> By: What’s in your wallet? | iLude http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-190 What’s in your wallet? | iLude Sat, 28 Feb 2009 05:24:32 +0000 http://www.noctovis.net/blog/?p=66#comment-190 [...] on the stir that occurred after Stack Overflow #38. I’m firmly on the side of the apparent “SOLID”-nista’s. The reasons for this is that learning and applying them has made me a better [...] [...] on the stir that occurred after Stack Overflow #38. I’m firmly on the side of the apparent “SOLID”-nista’s. The reasons for this is that learning and applying them has made me a better [...]

]]> By: Design principles « Yoot http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-156 Design principles « Yoot Tue, 24 Feb 2009 00:05:07 +0000 http://www.noctovis.net/blog/?p=66#comment-156 [...] Design Principles [...] [...] Design Principles [...]

]]> By: Nocturn vision » Blog Archive » Code-review with NDepend http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-93 Nocturn vision » Blog Archive » Code-review with NDepend Mon, 09 Feb 2009 20:29:40 +0000 http://www.noctovis.net/blog/?p=66#comment-93 [...] There are some queries that can help you check if the developers respected the most important design principles: [...] [...] There are some queries that can help you check if the developers respected the most important design principles: [...]

]]> By: Design Principles « Sweet Blog http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-73 Design Principles « Sweet Blog Wed, 04 Feb 2009 12:04:05 +0000 http://www.noctovis.net/blog/?p=66#comment-73 [...] suis tombé récemment sur un excellent post concernant les principes de bases du développement orienté objet. On y trouve une description de [...] [...] suis tombé récemment sur un excellent post concernant les principes de bases du développement orienté objet. On y trouve une description de [...]

]]> By: Nocturn vision » Blog Archive » The use of partial classes http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-65 Nocturn vision » Blog Archive » The use of partial classes Mon, 02 Feb 2009 18:39:41 +0000 http://www.noctovis.net/blog/?p=66#comment-65 [...] it up to keep it bearable to even read it, you’ve seriously been messing around with the SOLID principles, the DRY principle, and God knows what more… Thus, it’s time to think and [...] [...] it up to keep it bearable to even read it, you’ve seriously been messing around with the SOLID principles, the DRY principle, and God knows what more… Thus, it’s time to think and [...]

]]> By: rowan http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-55 rowan Fri, 30 Jan 2009 00:25:42 +0000 http://www.noctovis.net/blog/?p=66#comment-55 thanks, i'll check out the book. thanks, i’ll check out the book.

]]> By: Laila http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-50 Laila Wed, 28 Jan 2009 06:34:35 +0000 http://www.noctovis.net/blog/?p=66#comment-50 Hi Rowan, I can't say I learned them all on the job, unfortunately. I don't have that much of experience either (I've been working for about 3 years now). I guess it was the will to always improve my code, by reading books and blogs that I gathered them all up. But as I said, if you just read the book Agile principles, patterns & prinicples in C#, you'll know them all in a few hours ;) Hi Rowan, I can’t say I learned them all on the job, unfortunately. I don’t have that much of experience either (I’ve been working for about 3 years now). I guess it was the will to always improve my code, by reading books and blogs that I gathered them all up. But as I said, if you just read the book Agile principles, patterns & prinicples in C#, you’ll know them all in a few hours ;)

]]> By: rowan http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-49 rowan Tue, 27 Jan 2009 23:40:22 +0000 http://www.noctovis.net/blog/?p=66#comment-49 out of curiosity, how did you learn all this stuff? self taught through many years of experience? help from colleagues? I'd never come across many of these principles before I started reading blogs etc.. out of curiosity, how did you learn all this stuff? self taught through many years of experience? help from colleagues? I’d never come across many of these principles before I started reading blogs etc..

]]> By: Laila http://www.noctovis.net/blog/index.php/2009/01/15/design-principles/comment-page-1/#comment-41 Laila Tue, 27 Jan 2009 11:52:36 +0000 http://www.noctovis.net/blog/?p=66#comment-41 @Jonathan: Thx for your interest. I've read your AMMERSE principles, and I found them very interesting. I think I can summarize each one of them as being the goal of at -least- one of the principles I've explained above. When applied as they should be applied, the software you'll be producing corresponds to your AMMERSE principles (extensible, agile, minimal, maintainable, solving and environmental). The only one that doesn't fit into the <i>OO design principles</i>, is ReachableDesign, but this isn't a principle you can apply to OOP. This one applies to a larger scope (your project) and I think you can achieve it by applying scrum (with user stories and sprint demo's) and continuous integration :) , but this wasn't the scope of my post. @Rowan & @Duj: thx for your interest :-) @Jonathan: Thx for your interest. I’ve read your AMMERSE principles, and I found them very interesting.
I think I can summarize each one of them as being the goal of at -least- one of the principles I’ve explained above. When applied as they should be applied, the software you’ll be producing corresponds to your AMMERSE principles (extensible, agile, minimal, maintainable, solving and environmental).
The only one that doesn’t fit into the OO design principles, is ReachableDesign, but this isn’t a principle you can apply to OOP. This one applies to a larger scope (your project) and I think you can achieve it by applying scrum (with user stories and sprint demo’s) and continuous integration :) , but this wasn’t the scope of my post.

@Rowan & @Duj: thx for your interest :-)

]]>