Long-term reliability test with Django
But this website, built by hand using Django, has held up remarkably well over time.
A little history: I built this site a few years ago when Lindsay and I lived in Knoxville, TN. I was working for the E.W. Scripps company at the time, and had a full-on love affair with Django (I still do).
I started working at Scripps at the beginning of the first enterprise rollout of a Django content management system (customized version of Ellington. I was not new to Django then; I began using the framework toward the end of our first stay in Roanoke.
This blog was both a way for me to keep my writing chops pliable, but also to put into practice the code used by Scripps developers. It helped me understand what they were building, and apply that knowledge to my role as project manager.
As new versions of Django came out, so did this blog. I stopped updating around version 1.2.3 however.
But unlike a WordPress install, this app has continued to hum along dutifully.
This isn't to say I recommend building apps and not maintaining them. I plan to update this app to the latest version of Django soon.
Until that time, it's good to know that this venerable framework, put to use in the right way, can produce reliable web applications that stand the test of time.