Slashdot Mirror

← Back to Stories (view on slashdot.org)

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

Posted by Soulskill on 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?"

3 of 360 comments (clear)

  1. Re:one question by SuperMooCow · · Score: 4, Funny

    10 print "Yes we do."
    20 print "You're looking at it."
    30 end

  2. Re:no by Samantha+Wright · · Score: 3, Funny

    Oh code quality? Just from looking at the tags I thought this was a story about cod equality. Damn those herrings.

    --
    Bio questions? Ask me to start a Q&A journal. Computer analogies available for most topics!
  3. Awful code by WaffleMonster · · Score: 3, Funny

    Don't whine.

    Don't use TDD.

    Don't assume use of modern language features yield better code.

    http://xkcd.com/610/