News for hackers. Stuff that matters.
Re:How to Improve a Legacy Codebase by _pmf_ on Tuesday May 30, 2017 @10:45AM (#14445710)
> At the very least, write a doc that explains how to build the product, including where to find the parts in source control, what the dependencies are, what servers it'll get installed on, and so on.

... in the form of a Jenkins build configuration. (If possible; if the system requires legacy compilers that only run on old Windows versions or a proprietary compiler for an embedded target, good luck.)

Re:How to Improve a Legacy Codebase by chiph on Tuesday May 30, 2017 @11:08AM (#14445875)
The legacy projects are the ones where a doc with all that info would be the most useful. :)