I have been involved with a project that has been using cvs for the longest time. Over the years, a great deal of experience has been acquired in source control management, processes and tools have evolved to reflect that knowledge. A lot of third-party tools like wikis, bug trackers, etc. actively maintain git plug-ins. Cvs is increasingly an afterthought, for very good reasons. So despite everything running smoothly with cvs for now, it won't be long before sticking with cvs becomes a huge technical debt. read more...

Many times while validating a software product, you have to substitute a few parts in order to enable automated testing. This was again the case recently when I was confronted with a java application built as a jar file. The application relied on a complex subsystem of components that needed to be stubbed out in the test runner. read more...