SkelVA writes: "I'm sure anyone who has maintained a legacy system has dreamed of porting to the new technology hotness of the time. This post explains how and why a company made that decision and converted from php to django over the course of almost two years. "We took the position that the PHP portions of our application were just pieces of code that needed refactoring. Once we made that decision our process naturally fell out; we already knew how to handle less-than-perfect code. When we added new features, they were done in Python and Django. When we needed to polish or otherwise fix functionality that lived in PHP, we looked at it just like you'd look at that super-ugly method you wrote a couple of years ago when you were in a hurry. If it was a very small change, we tended to just make the change in PHP. If it was a decent chunk of change, or the change would be easier in python, we first wrote unit tests on what we expected the behavior to be using the existing code as a guide, then we ported the code to Django and made the fix. During that time, we continued to deliver regular product updates.""
Repel them. Repel them. Induce them to relinquish the spheroid.
- Indiana University fans' chant for their perennially bad football team