Does anyone else get frustrated by the fact that most
software developed today is built by someone who
(equivelent to building a house), shows up with a truck
full of wood and a nail gun, ... thump thump thump ...
starts building it with no previous thoughts to design or
software engineering best practices.
Doug,
You're not alone. I'm just starting a project for a client who are
on their third attempt to build an app.
The first person(*) (an employee) threw together a couple of forms
and then left for greener pastures, w/o leaving any documentation or
source code(!).
The second person(*) (an outside consultant) also built a couple of
forms, then got frustrated and withdrew from the project. He
apparently has a conscience in that he told the client there would be
no charge for the partially completed work. Like the first guy, he
left behind no source code or documentation.
( (*) I refuse to call these people "developers" because they simply
didn't develop anything.)
Then the desperate client calls me. This is the third time *this
year* I've faced a "clean up someone else's mess" scenario (all w/
different clients).
I obviously feel sorry the clients. It's our responsibility to know
our own capabilities as software development professionals, and to
inform the client if we're not able to provide the services they
need.
I also feel a combination of pity and anger towards the people who
cause these wrecks. Anger for the obvious reasons, and pity because
it would only take some well-directed education to turn these people
into assets instead of liabilities.
I think that's enough ranting
. As for solutions, aside from
expanding one's personal knowledge base, I'm not aware of any
realistic quick fixes for our profession as a whole. Steve McConnell
has written an excellent book on the subject of the future of the
profession of software engineering called "After the Gold Rush". If
Mr. McConnel is correct - and I think he is - we've got a lot of
work to do yet.
Chris.