Shared publicly  - 
Technical debt will kill you dead (if you let it) -
mustafa daragmah's profile photoAnardo Cuello's profile photochristopher sebetero's profile photoVb Wyrde's profile photo
Nice article, I definitely know the horrors of maintaining another's code-base and find the tips laid out in this article will go far in easing other people's headaches that have to deal with this sort of thing as a day job.
Amen!  Fully agree that you need to keep the tech debt to a minimum and make every effort you can to burn any that you may have accrued.  Otherwise, your site, app, house of cards, whatever will collapse and when it does it will be quick and painful and I'm speaking from experience.  
This is my comment to the article, which I'm also posting here...
I wonder how a tiny one-person startup should go about following this advice?  I agree that having a pre-go-live review of the code base is a great idea, and cleaning up before launching is the best plan.  But how to find good competent reviewers who will do the right thing and make good recommendations?  ... that won't cost a Godzillion $$$?   There's a lot of one-person shops out there producing code and hoping to get it online and enthusiastic users, but who don't necessarily have a lot of working capital to start with.  What approach might you recommend in that scenario?
If you have clearly defined business requirements and use cases for your site/app/tool/etc and you follow best practices in development then you should be able to crowdsource your code review process at a fairly low costs.  There are things to consider though before turning your source code over to just anyone you find online to do a code review, but there are sites out there where you can find good & trusting peers to review your code.  
What sites would you consider, and how would you know who is good & trustworthy?
Great article! Developers know very well what this feel like.
Frankly I think it's a bit overstated.  I've had to go in and clean up someone elses pretty crappy (and I mean CRAPPY) code and SQL.  Took a few weeks.  Ok, loss of productivity in terms of a new project, but it wasn't that horrible.  Just clarified, organized, and went to work.  Three weeks later... voila.  Pretty, documented and clean.  All done.  Next.
Add a comment...