Monday, October 10, 2016

Software stagnation - Doing nothing can cost you money

I have been writing Microsoft Access software now for nearly 25 years. In that time I have occasionally had software projects that have not had any development or support for 5 years or more. If the project was small, starting again is no trouble. If the project was big, getting back on top of the project is either costly to me or the customer.

After 5 years has gone by, the customer will be familiar with what some of the software does but may not be aware of the workings/specifications for the software, especially if they are new to the company. If so then everyone who is going to be involved in the new development will be "somewhat in the dark".

Things can get start to get a lot darker when the programmer of the software leaves town. Given that there has been no action (read money) for five years, there is every likelihood that they will have left town. This particularly applies to contract programmers who are working on the next project the minute the current contract is completed. My company doesn’t do contract jobs for that very reason.

 What is the solution to this stagnation dilemma ?

  Read the full editorial on Linked-In here


A potted plant in the lovely Fiesole near Florence, Italy

No comments: