Fragile – Handle With Care
IMHO, this is the worst phrase to hear about your software system, only surpassed by the worse phrase, do not touch.
Fragile software is probably the worst scourge of a any product. If so, why is it a common occurrence?
Fragile code is often not extensible; new features can’t be added to it. Other times it is immobile; the code may have too many dependencies to be used in applications other than the original code. Other times it is un-testable; software patterns have not been employed allowing the code to be tested in any fashion, automated or manual.
Sometimes you recognize this problem when you see a method or procedure with so many lines of code, and levels of nested if statements or loops, that you can’t determine what code is included in the IF or the loop.
I’m sure, if you have been working with software for more than a couple of years, canned or custom, you have experienced fragile software. Why not share with us some of your experiences? You could share practices or situations you have experienced leading to fragile code. Maybe you have something you could share about the results of fragile code?
Send your comments to btaylor@sswug.org.
Cheers,
Ben
SSWUGtv
What is a personal commitment plan, and how can you get your boss to agree to one? Laura Rose is back on the show with some helpful tips.
Watch the Show
$$SWYNK$$
Featured Article(s)
Total Database Information At Your Fingertips (Part V)
This article will help to get some basic information from your databases that may help you in different situations.
Featured White Paper(s)
Go Beyond SCOM Monitoring with Foglight for SQL Server
read more)
Featured Script
GetObjNameList
This stored procedure can be used to return the names of the tables, constraints, stored procedures, views, rules and trigge… (read more)