Did you know? DZone has great portals for Python, Cloud, NoSQL, and HTML5!

Justin Etheredge is a Senior Consultant for Dominion Digital in Richmond, Virginia - United States. He likes to blog quite a bit at http://www.codethinked.com with hopes that someone out there might read it. When he isn't writing software or working on his computer... wait, he is always doing that. Anyways, Justin likes programming, a lot. Justin has posted 24 posts at DZone. View Full User Profile

Why Do We Keep Building Tightly Coupled Software?

07.06.2009
Email
Views: 3437
  • submit to reddit

A good friend of mine, Kevin Israel, said on twitter today:

"how freakin long are *we* gonna keep building tightly coupled software that needs to constantly evolve!?"

At first I wanted to say "until programmers stop sucking so much", but unfortunately, there is often much more to the picture than the usual "you're surrounded by idiots" response. Many of us do continue to build tightly coupled software, and we do it for a variety of reasons. Some of us just don't know any better, we've never been exposed to or experienced what exactly people mean by "loosely coupled" software. Others see creating loosely coupled software as another layer of complexity that they just don't need inside of their applications. And yet others, have seen and experienced it, but still don't understand how to implement it effectively. Unfortunately, at this point I think that majority of developers fall into the first camp, they just don't know what it means to build "loosely coupled" software.

Read the rest of this post at CodeThinked.com

References
Published at DZone with permission of its author, Justin Etheredge. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

Christian Posta replied on Mon, 2009/07/06 - 2:40pm

I honestly believe that the biggest problem that most developers have is that they take action without considering the reasons or implications

 I agree, although I would take it a step further. Most developers might take action without considering the reasons or implications because 1) they don't want to invest the time to learn 2) it's easier to not. A lot of developers show up to work 8 hours and collect a pay check. Pushing themselves to better their skills and improve their understanding of software construction seems not to be on their 'to-do' list.

Adam Carbone replied on Tue, 2009/07/07 - 11:45am in response to: christian.posta

I think that a huge portion of this is caused by the managers not getting it. If you do get the rare few that do get it, there bosses putting them under pressure to just do what works to get it done now. We will worry about later when later is here, and you get a balance of when you can do it the right way vs when you jsut use bandaids and bubblegum. Then you get a ton of technical debt to payback...

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.