Is that the right philosophy to follow? Or should you not put off till tomorrow what you can do today? For the answer, think "upgrade."
Written by Barry L. Kline
If it ain't broke, don't fix it.
That old adage has been around since the Carter administration. The down-home advice seems so logical and obvious that everyone may feel compelled to follow it. I know that with my busy schedule, it's easy for me to put off updating software on working systems when there are far more pressing projects to tackle. If you're willing to admit it, you probably can point to a system or two under your control that could use some tender, loving care. Unfortunately, following the "if it ain't broke" philosophy can readily lead to minor irritations and downright spectacular failures. You'd think that 30 years in this business would have provided me with enough opportunities to learn this lesson and that I would have it indelibly imprinted in my mind. But no, I fell into the trap once again.
Learn how to support a multiple-developer version-control environment using source-code hosting for git repositories.
Written by Tom Snyder
Has your shop begun using multiple programming languages? The implementation of new options may not be on the top of the priority list. Code can be developed, priorities could change, staff could change, and by the time you go back to complete something you initiated a few months ago or try to find the source code for something that is deployed, you may have difficulty determining where the source code is or what version was actually deployed. This is where git can help.
Written by Barry L. Kline
Written by Tom Snyder