The Artima Developer Community
Sponsored Link

Java Buzz Forum
Software value in design perfection.

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
scot mcphee

Posts: 75
Nickname: scotartt
Registered: Feb, 2004

Scot Mcphee is a Java/J2EE developer for Kaz Technology Services in Sydney, Australia.
Software value in design perfection. Posted: May 20, 2005 6:57 PM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by scot mcphee.
Original Post: Software value in design perfection.
Feed Title: SystemExxception()
Feed URL: http://www.autonomous.org/pebble/systemexxception/rss.xml?category=Java
Feed Description: java design and culture by scot mcphee
Latest Java Buzz Posts
Latest Java Buzz Posts by scot mcphee
Latest Posts From SystemExxception()

Advertisement

Perfection is the mortal enemy of good. A collary from politics; The road of idealism leads straight to the gates of the death camp.

Value-for-money and fit-for-purpose are business decisions. Businesses don't care about OO technique, the Law of Demeter, architectural principles, separation of concerns and cyclic dependencies, they care whether their order-entry system enables them to enter orders (or whatever). Try telling the business you want to fix the design because the new design you have in mind is "better" and they will ask what new features they get for their money, and if you can't rattle that off they will say the IT department is paying for the re-engineering (exactly where we are now with the current project). The business is worried that we just did three months of development effort and even though they are not paying for it, that's three months where the amount of visible features in the system has increased negligibly.

On the other hand the cost of maintenance is also a business concern if they are paying for maintenance. Therefore of course, over the longer term, all those things like cyclic dependencies and so on do affect the business, but the business' view of the matter is at a different level of abstraction than ours (as software developers).

The real problem I believe here is the question of timeframes. To a business, short term often means the next quarterly statement and long term means to the end of the financial year. In my view, this is an issue that affects the way businesses operate and their decision making in general, it generates a lot of market distortions because people rarely think about 5 years away - about 2 years appears to the current business (and social) horizon. Fix that problem (HA!) and you will find the issues with software development are frequently also alleviated.

Read: Software value in design perfection.

Topic: HTTP GET versus POST controversy in light of Google Web Accelerator fiasco and How Google can... Previous Topic   Next Topic Topic: United We stand

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use