Hacker News new | past | comments | ask | show | jobs | submit login

My experience says that for real legacy code (deployed and actually used) it is almost always better to slice it up and re-write and deploy sections of it incrementally. Big-bang transitions with a "point of no return" are just so expensive and risky.

Yes, you lose "conceptual integrity" and your UX may be inconsistent in the transitional time, but those are small prices to pay.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: