<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://tod1d.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Article of the Week: Things You Should Never Do, Part I (aka Old Code != Bad Code)</title><link>http://tod1d.net/blogs/tech/archive/2008/04/08/Article-of-the-Week_3A00_-Things-You-Should-Never-Do_2C00_-Part-I-_2800_aka-Old-Code-_21003D00_-Bad-Code_2900_.aspx</link><description>Title: Things You Should Never Do, Part I (aka Old Code != Bad Code ) Author: Joel Spolsky Comments: This is an oldie, but a goodie. It is a reminder, to me, why rewriting an existing application can be both a financial and strategic mistake. Sometimes</description><dc:language>en</dc:language><generator>CommunityServer 2.1 (Build: 60809.935)</generator></channel></rss>