Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Back for a limited time - Get 15% off sitewide on Slashdot Deals with coupon code "BLACKFRIDAY" (some exclusions apply)". ×

Submission + - Ask Slashdot: How to Avoid Working With Awful Legacy Code

kramer2718 writes: I have worked for about a decade as a software engineer. I am almost never hired to build new software from scratch, so my work satisfaction tends to be proportionate to quality of the legacy code I have to work with. Some legacy code has been good. Most of it is bad. I know a few questions to ask during an interview to determine the code quality: Are recent technologies used? Are there code review processes? Is TDD practiced? Even so, I still encounter terrible quality code. Does Slashdot have any advice for other questions to ask? Any other ways to find out code quality beforehand?
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Ask Slashdot: How to Avoid Working With Awful Legacy Code

Comments Filter:

Never say you know a man until you have divided an inheritance with him.