I read that another way. The whole article sounded like they replaced engineering with hacking/prototyping and measuring the productivity of a prototype vs the

I read that another way. The whole article sounded like they replaced engineering with hacking/prototyping and measuring the productivity of a prototype vs the productivity of battle-hardened code. There is an admission that they have no specs and i also got the impression that they have no tests. I seriously doubt that at the claimed turnaround times they have a proper code review process. It sounded to me like they were getting false productivity and eventually would program their way back into a corner. Having been on a team where the pendulum has swung both ways I know firsthand that you can be too agile and end up regretting it later.