News for hackers. Stuff that matters.
Re:Code sucks by jokull on Saturday December 01, 2012 @10:01AM (#4857789)
Right on. This is related to "the big rewrite" that kills a lot of projects. Time and usage makes code value go up. Even if it’s written in an old framework that you wouldn’t use today, uses urllib instead of requests. Just ignore the urge and move on (for now).

I’ve recently worked on an old project (www.oath.is), dusted it and launched it as an app. It was a Django project and my urge was to rewrite the whole thing so I could use SQLAlchemy and Flask which I had picked up in the meantime. On the frontend I immediately wanted to rewrite everything in CoffeeScript and Backbone.js. But I resisted it and managed to spend my time adding features, a new design and unit tests and launched in like a week. After launching I had some extra time to rewrite the jQuery-spagetthi, which paved the way for some more advanced client side features without becoming a horrible mess. So I guess you have to make that decision multiple times over the lifetime of a project. But yes, holding off the urge is a good practise.

Re:Code sucks by j-kidd on Saturday December 01, 2012 @11:13PM (#4860057)
When the existing code base is at least functional, then of course, a big rewrite is not warranted.

However, some of us are not as lucky. The situation is often such that the existing code base is full of bugs that it can cause a ton of support requests from the users, or even crash and bring down the production server.

In such situation, you can choose to firefight all days and have no time left to implement new stuffs, or choose to rewrite.

Not using the latest hippiest libraries is really the least of my problem.

Re:Code sucks by jokull on Sunday December 02, 2012 @04:24AM (#4860670)
Agreed. When it comes to code that’s "not exactly how I would have done it" but _also_ bug ridden I think it’s an easy decision.
Re:Code sucks by LeonidBugaev on Saturday December 01, 2012 @10:12AM (#4857817)
Thanks! Exactly what i mean.