3 ms·
The obvious question is: how large was your team? While a lot of the commenters here seem somehow outraged at the computations, 5.5 man years seemed like a ver
by jsnell 13y ago
The obvious question is: how large was your team?
While a lot of the commenters here seem somehow outraged at the computations, 5.5 man years seemed like a very aggressive schedule for rewriting a 1MLOC system, even if the end result were a 100KLOC one. My initial guess would have been 10 man years, and a cost in the millions.
So here you have what was probably a 150KLOC original system. How many man-years would you guess the rewrite took?
- anarchitect 13y agoThree, plus a part-time contractor. One of the team is front-end so had little to do with replacing the Perl part. The truth of it is, in our case it isn't (yet) a full rewrite, and there is still a lot of functionality tied up in the existing codebase. So it's not easy to answer the question about man years, but I would guess around 1.5. The biggest wins for us in terms of lines of code were not the language (we did consider sticking with Perl), but re-assessing the business logic, ridding the codebase of legacy junk and using existing libraries instead of hand-rolled solutions.
- bluej4ack 13y agoThe way you did it seems to be the most logical (and obvious) approach, which the article completely neglects to mention