Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
Log in  ::  Register  ::  Not logged in


By Steve Jones,

I stumbled upon an old blog post by Neil Davidson that he recycled via Twitter. It was about design and how things bloat. In the post he references another blog by Moishe Lettvin , who worked on the Shutdown menu in Vista. Reading that post, I was amazed to find that 8 people directly and 43 people indirectly contributed to that feature over a year.


At first I had the amazing response that most people probably have of MS is obviously so (insert your four letter adjective here) blanked-up, no wonder Vista was late. However as I read through the comments, I saw so much disagreement over how the feature works, should work, compares with OS X, and more that I'm not sure so this was a year of development time wasted. (Note I don't know the man-years spent on this, but I bet it's > 1).

I haven't built a lot of software in my career, especially large scale or shrink wrap software, and so perhaps I don't really understand things. However I do think that we tend to over-engineer too often. I see people that try to design in every contingency, as well as think of every possible places things might go wrong. I have a simple mantra for you folks:

You can't do it. Get over it and ship something.

It sounds simple, but it's not. But it's not necessarily naïve. I've seen too many people delay releasing something, trying desperately to get things right. They're never right. They're also never done, so you might as well ship something that's 80% right and then plan on fixing it right away.

I know some people will disagree and say that things should be built right the first time. I don't think they ever are. They can be built well, but they ought to be built quickly, and with a design that expects changes to be required in  a relatively short time frame after they're released. This doesn't work for all software, but I bet it works for a large class of applications that aren't on the scale of SAP or Windows.

We can learn to code better, build more secure and stable software, but I don't think we'll ever cover all the bases. So why try? Build something that works most of the time and then refine it from there.

Steve Jones

The Voice of the DBA Podcasts

Everyday Jones

The podcast feeds are available at Comments are definitely appreciated and wanted, and you can get feeds from there.

You can also follow Steve Jones on Twitter:

Overall RSS Feed: or now on iTunes!

Today's podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at

I really appreciate and value feedback on the podcasts. Let us know what you like, don't like, or even send in ideas for the show. If you'd like to comment, post something here. The boss will be sure to read it.

Total article views: 158 | Views in the last 30 days: 1
Related Articles

Podcast Announcements

Podcast Feeds


Technical Podcasts I Listen To

There are a few podcasts I tend to listen to as I have time. Since I work with a wide...


Podcast Problem

Podcast Problem Blocked by group policy



A new video setup is on the way!!!! Actually I'll do a couple podcasts on podcasting over the hol...


Practicing Deployments

Amateurs practice until they can get something right. Professionals practice until they don't get th...


Join the most active online SQL Server Community

SQL knowledge, delivered daily, free:

Email address:  

You make SSC a better place

As a member of SQLServerCentral, you get free access to loads of fresh content: thousands of articles and SQL scripts, a library of free eBooks, a weekly database news roundup, a great Q & A platform… And it’s our huge, buzzing community of SQL Server Professionals that makes it such a success.

Join us!

Steve Jones

Already a member? Jump in:

Email address:   Password:   Remember me: Forgotten your password?
Steve Jones