News for hackers. Stuff that matters.
Re:As Digg Struggles, VP Of Engineering Is Shown The Door by davidw on Wednesday September 08, 2010 @03:51AM (#1671324)
> incremental rewrite of parts of the unmaintainable spaghetti classic

Sounds good in theory. In practice? Part of the problem with many big ball of mud systems is that all the parts depend on and talk to all the other parts. Want to fix that horrid DB schema? You'll have to rewrite all the code that talks to it, or rewrite it to talk to an intermediary. Want to rewrite that horrid bit of code that's called foobar_20040623 ("foobar" has been changed, but yes, I saw this in some PHP code...), you'll have to find out what all it interacts with, and likely redo that too.

Re:As Digg Struggles, VP Of Engineering Is Shown The Door by MartinCron on Wednesday September 08, 2010 @01:47PM (#1672687)
In practice? It's not easy, but nothing is. I see three options to the big ball of mud problem.

1. Wallow in it (work with existing structure). Sadly, this is what a lot of people do. I left a job once because that was the only way out of the ball of mud. I was afraid I would turn into a mud-person.

2. Slowly crawl out of it (incremental rewrite). This is hard, but do-able. It involves setting up barriers to mitigate ripple effects, automated testing to be comfortable with frequent releases, and tolerance for temporary imperfection (basically, you need to be willing to frequently release things that are only a tiny bit better than status quo, even if it's not ideal). Not everyone is willing to accept this persistent imperfection and lack of conceptual consistency, especially when option #3 is more exciting and fun.

3. Try to leap out of it and land wherever (total rewrite). This is very, very hard, and prone to total failure or spending valuable money and time to effectively stand still in the market.

I've seen development teams leap directly out of one ball of mud into a different one. One where nobody even knew their way around anymore. How is that anything but a huge waste of time and resources?

Re:As Digg Struggles, VP Of Engineering Is Shown The Door by davidw on Wednesday September 08, 2010 @02:55PM (#1672985)
Fascinating topic - lots of startup talk is fun because you get to do things from scratch, but this is very pertinent to the Real World.

In terms of "standing still in the market", I think the incremental rewrite contains a lot of that too, no? It's just spread over more time. You're still rewriting it, and during that time, you're not adding new features. An example might be retrofitting some testing code to a system that's never had test code. That could potentially be a fair amount of work, and given a constant pool of resources, it will take time away from "new stuff". Just that it's not so much of a quantum leap - you can still drop your new testing code and go implement some must-have feature if you need to, without saying you have to wait for the whole thing to be ready.

Sadly though, my experience in this is that the reason there's a ball of mud in the first place is a political/social one, so that any "dead time" is frowned upon.

Re:As Digg Struggles, VP Of Engineering Is Shown The Door by rwmj on Wednesday September 08, 2010 @08:15AM (#1671605)
In reality yes, it works, I've done it. We took a horrible, accreted web application, and rewrote it in stages over a period of about 12 months. At the same time we were making regular releases, and needless to say the site stayed up the whole time.

You just have to plan things carefully, work hard, and keep your head screwed on. (Just like with many things in life ...)

Re:As Digg Struggles, VP Of Engineering Is Shown The Door by davidw on Wednesday September 08, 2010 @12:05PM (#1672278)
This would make a great topic for blogs/books/whatever. "How to dig yourself out of a pile of shit."
Re:As Digg Struggles, VP Of Engineering Is Shown The Door by MartinCron on Wednesday September 08, 2010 @01:51PM (#1672701)
I agree, although it's a somewhat sensitive thing to write about if you're doing it in practice. I sure as hell don't want to be known as the guy who comes in and calls all of the existing code a pile of shit.

I guess I could "change the names to protect the innocent" and tell some stories about digging out of tight places incrementally. If it would convince even one development team that they didn't absolutely have to do a total rewrite, it would be worth it.