Ask Slashdot: How To Avoid Working With Awful Legacy Code?

Posted by Soulskill on Tuesday October 23, 2012 @01:05PM from the flex-your-burger-flipping-skills dept.

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?"

1 of 360 comments (clear)

Min score:

Reason:

Sort:

Re:any questions? by Anonymous Coward · 2012-10-23 21:11 · Score: 5, Informative

My brother who works in construction does the same thing. He calls it the "fuck off quote". Most people turn you down and you walk away with a smile. A few accept but you're on triple rates so you do the job, however shitty, with a smile.