On the need for re-architecting

I have been grappling with the concept of a rewrite of a relatively successful software product that I've been involved with since start-up mode. In truth I was googling for compelling stories about why NOT to disappear for a year to do a complete re-engineering of your product (ala Netscape). Mostly because I'm concerned about the size of the effort and the resources we have to pull it off. Instead came across this article, espousing the need to fire all your developers!


Well I'm the guy who's been promoted to a more senior developer role (not architect, our group shares that responsibility) but still by Mike's logic the guy who should be fired (?!). I'm the guy who now is learning the ropes in management and who happens to really know the product and the business but now swimming in very exciting waters when it comes to our rearchitecting plans.

What I do have going for me is an incredibly strong team to work with. I'm undecided yet as to whether we actually need an ivory tower architect or if our guys can work this with the guidance of our CTO. We'll see, as it's still not too late to change course.

In any case I think I'll keep an eye on more perspectives like Mike's...