sl4shd0t
08-05-2012, 11:46 AM
http://feedads.g.doubleclick.net/~at/ZNCaRBTcVlYThyliGX0hhCGaQbg/0/di</img> (http://feedads.g.doubleclick.net/~at/ZNCaRBTcVlYThyliGX0hhCGaQbg/0/da)
http://feedads.g.doubleclick.net/~at/ZNCaRBTcVlYThyliGX0hhCGaQbg/1/di</img> (http://feedads.g.doubleclick.net/~at/ZNCaRBTcVlYThyliGX0hhCGaQbg/1/da)
An anonymous reader writes "An article at Ars recaps a discussion from Stack Overflow about a software engineer who had the misfortune to inherit 200k lines of 'spaghetti code' cobbled together over the course of 10-20 years. A lengthy and detailed response walks through how best to proceed at development triage in the face of limited time and developer-power. From the article: 'Rigidity is (often) good. This is a controversial opinion, as rigidity is often seen as a force working against you. It's true for some phases of some projects. But once you see it as a structural support, a framework that takes away the guesswork, it greatly reduces the amount of wasted time and effort. Make it work for you, not against you. Rigidity = Process / Procedure. Software development needs good processes and procedures for exactly the same reasons that chemical plants or factories have manuals, procedures, drills, and emergency guidelines: preventing bad outcomes, increasing predictability, maximizing productivity... Rigidity comes in moderation, though!'"http://a.fsdn.com/sd/twitter_icon_large.png (http://twitter.com/home?status=How+To+Deal+With+200k+Lines+of+Spaghet ti+Code%3A+http%3A%2F%2Fbit.ly%2FOCyeow)http://a.fsdn.com/sd/facebook_icon_large.png (http://www.facebook.com/sharer.php?u=http%3A%2F%2Fdevelopers.slashdot.org% 2Fstory%2F12%2F08%2F05%2F040248%2Fhow-to-deal-with-200k-lines-of-spaghetti-code%3Futm_source%3Dslashdot%26utm_medium%3Dfacebo ok)http://www.gstatic.com/images/icons/gplus-16.png (http://plus.google.com/share?url=http://developers.slashdot.org/story/12/08/05/040248/how-to-deal-with-200k-lines-of-spaghetti-code?utm_source=slashdot&utm_medium=googleplus)
Read more of this story (http://developers.slashdot.org/story/12/08/05/040248/how-to-deal-with-200k-lines-of-spaghetti-code?utm_source=rss1.0moreanon&utm_medium=feed) at Slashdot.
http://feeds.feedburner.com/~r/Slashdot/slashdotDevelopers/~4/DFZf36DWYC4
More... (http://rss.slashdot.org/~r/Slashdot/slashdotDevelopers/~3/DFZf36DWYC4/how-to-deal-with-200k-lines-of-spaghetti-code)
http://feedads.g.doubleclick.net/~at/ZNCaRBTcVlYThyliGX0hhCGaQbg/1/di</img> (http://feedads.g.doubleclick.net/~at/ZNCaRBTcVlYThyliGX0hhCGaQbg/1/da)
An anonymous reader writes "An article at Ars recaps a discussion from Stack Overflow about a software engineer who had the misfortune to inherit 200k lines of 'spaghetti code' cobbled together over the course of 10-20 years. A lengthy and detailed response walks through how best to proceed at development triage in the face of limited time and developer-power. From the article: 'Rigidity is (often) good. This is a controversial opinion, as rigidity is often seen as a force working against you. It's true for some phases of some projects. But once you see it as a structural support, a framework that takes away the guesswork, it greatly reduces the amount of wasted time and effort. Make it work for you, not against you. Rigidity = Process / Procedure. Software development needs good processes and procedures for exactly the same reasons that chemical plants or factories have manuals, procedures, drills, and emergency guidelines: preventing bad outcomes, increasing predictability, maximizing productivity... Rigidity comes in moderation, though!'"http://a.fsdn.com/sd/twitter_icon_large.png (http://twitter.com/home?status=How+To+Deal+With+200k+Lines+of+Spaghet ti+Code%3A+http%3A%2F%2Fbit.ly%2FOCyeow)http://a.fsdn.com/sd/facebook_icon_large.png (http://www.facebook.com/sharer.php?u=http%3A%2F%2Fdevelopers.slashdot.org% 2Fstory%2F12%2F08%2F05%2F040248%2Fhow-to-deal-with-200k-lines-of-spaghetti-code%3Futm_source%3Dslashdot%26utm_medium%3Dfacebo ok)http://www.gstatic.com/images/icons/gplus-16.png (http://plus.google.com/share?url=http://developers.slashdot.org/story/12/08/05/040248/how-to-deal-with-200k-lines-of-spaghetti-code?utm_source=slashdot&utm_medium=googleplus)
Read more of this story (http://developers.slashdot.org/story/12/08/05/040248/how-to-deal-with-200k-lines-of-spaghetti-code?utm_source=rss1.0moreanon&utm_medium=feed) at Slashdot.
http://feeds.feedburner.com/~r/Slashdot/slashdotDevelopers/~4/DFZf36DWYC4
More... (http://rss.slashdot.org/~r/Slashdot/slashdotDevelopers/~3/DFZf36DWYC4/how-to-deal-with-200k-lines-of-spaghetti-code)