The only way to completely understand the system and therefore solve the logic problem - is to become totally immersed in it. This takes time. Often you will find that the system itself needs to be modified to solve the logic problem correctly, and modifying the system will have an adverse effect on other components which live in the environment you wish to change. The correct answer may indeed involve only four lines of code, but it can sometimes take days to know that.
The other aspect of rapidly designed software which makes it a poor business choice is that one must anticipate that the person who created the code will not be the same person who ends up maintaining it. If that person doesn't have sufficient information about why certain design choices were made (and how the function fits into its environment), the function - or even the entire system - will someday need to be scrapped. Over 90% of the software code ever written has eventually been scrapped.
Murphy strikes. During one of the hottest weeks in history, the air conditioner at the store decides that it can't take it anymore. The few shoppers who have ventured out in the heat and think they'll get a refreshing breeze inside have been in for a shock. It's hotter in here than it is on the street. All the repairmen are booked for the next two weeks. Time for some fans and wet towels...
(Submitted by Ramiro Estrugo, restrugo@fateware.com)

Digg
Delicious
Netscape
Technorati