House of Cards Design Anti-pattern

Dude, I blew up the Demo!

Uri Lavi — Fri, 24 Apr 2009 13:05:34 GMT

I am sure, we are ALL familiar with the situation: Morning… The sun is shining, the birds are chirping

Dude, I blew up the Demo!

Uri Lavi — Fri, 24 Apr 2009 13:03:42 GMT

I am sure, we are ALL familiar with the situation: Morning… The sun is shining, the birds are chirping

Dude, I blew up the Demo!

Uri Lavi — Fri, 24 Apr 2009 13:00:22 GMT

I am sure, we are ALL familiar with the situation: Morning… The sun is shining, the birds are chirping

Dude, I blew up the Demo!

Uri Lavi — Fri, 24 Apr 2009 12:57:19 GMT

I am sure, we are ALL familiar with the situation: Morning… The sun is shining, the birds are chirping

Dude, I blew up the Demo!

Uri Lavi — Fri, 24 Apr 2009 12:52:09 GMT

I am sure, we are ALL familiar with the situation: Morning… The sun is shining, the birds are chirping

re: House of Cards Design Anti-pattern

arnold — Wed, 25 Feb 2009 06:12:10 GMT

Really nice,this made me remind of my previous professional life.........THankz

re: House of Cards Design Anti-pattern

John R — Fri, 20 Feb 2009 16:12:08 GMT

Wow, as other's have said, this sounds familiar. One of the issues that our development team deals with it is not the Cowboy Coder mentality, but the Cowboy manager. Thus causing the anti-pattern.The manager will send out requirements and come up with "rules" for fixing issues without even consulting the developers. Then the developers will be told, you need to code it this way because we've already told our partner how it needs to be, and it's going to be easier for them to code this solution. Yuck.

re: House of Cards Design Anti-pattern

PeterRitchie — Thu, 29 Jan 2009 17:34:49 GMT

@Rubio. Generally you have to re-iterate the concerns they should already be having. They should have quality concerns, they should have turn-around concerns, etc. Explain how refactoring will help in there areas. If they have none of these concerns, it's much harder to sell the fact that things need to change. If it's "upper management" you're trying to sell to, you'll almost always fail. Refactoring is just a part of iterative design that you must schedule. If you're trying to sell to your development manager, there's likely a disconnect there and you may never be able to "sell it". In cases like that, I would simply include refactoring in all time estimates for development (i.e. time to implement feature x would included refactoring and unit testing effort); and maybe start looking for another employer.

How do you sell refactoring

Rubio — Thu, 29 Jan 2009 10:44:05 GMT

This is painfully familiar. But here's my question.

How do you sell the refactoring effort to management?

I've tried to explain what the condition of the code-base is and what are the consequences when you try to maintain and/or extend the code (reliability, time needed to understand the code, bubble gum fixes etc). The management is always very understanding, but come the next project, the refactoring needs always get second priority. How do you convince management that "observation of working" isn't evidence of completeness?

Dew Drop - January 28, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - January 28, 2009 | Alvin Ashcraft's Morning Dew — Wed, 28 Jan 2009 13:47:52 GMT

Pingback from Dew Drop - January 28, 2009 | Alvin Ashcraft's Morning Dew

re: House of Cards Design Anti-pattern

Jason — Wed, 28 Jan 2009 06:16:43 GMT

This sounds in many ways like the project I'm working on at the moment - which started off as a Greenfield project and hasn't even been released yet. At least I can now describe the concern that has been sitting at the back of my mind for a few months now.

Arjan`s World » LINKBLOG for January 27, 2009

Arjan`s World » LINKBLOG for January 27, 2009 — Tue, 27 Jan 2009 21:22:11 GMT

Pingback from Arjan`s World » LINKBLOG for January 27, 2009

re: House of Cards Design Anti-pattern

Edi — Tue, 27 Jan 2009 19:26:21 GMT

Sadly this reminds me of the project I'm employed in.

House of Cards Design Anti-Pattern

DotNetKicks.com — Tue, 27 Jan 2009 15:54:07 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com