This post originated from an RSS feed registered with .NET Buzz by Doug Thews. Original Post: The Problem with Quick & Dirty S/W Development Feed Title: IlluminatiLand Feed URL: http://apps5.oingo.com/apps/domainpark/domainpark.cgi?client=netw8744&s=JETBRAINS.COM Feed Description: A technology blog for people enlightened enough to think for themselves Latest .NET Buzz Posts Latest .NET Buzz Posts by Doug Thews Latest Posts From IlluminatiLand

There's a good discussion on Slashdot about "Quick 'n Dirty" vs. "Correct and Proper"? in the world of software development


I've been manager on too many dev teams where there's too much pressure from the executives about skipping what I call the fundamentals of good software development.


The problem is that most executive "committees" go off and arbitrarily decide ideas, goals, and release dates without even consulting the technology people (and no, a CIO usually doesn't count because their too far removed from the real work). So, the end result is "here's what needs to be done, and we need it by ". Thus begins, the move to quick & dirty - because your job is on the line (how many times have I heard that one before?).