Mind that age! This blog post is 12 years old! Most likely, its content is outdated. Especially if it's technical.

From the django-users mailinglist which I'm becoming more and more helpful in:

> Could you share approximately how big your project is? I know it's > hard to find a real measure for this, but how about number of database > tables? A project I worked on over the summer used a Database that was 130 tables, and getting 1gb updates every 2 minutes. I was witting a new web app to do calculations on the data and the company wanted to use Java since thats what they knew best and had spend huge amounts of money (1 mil +) to support with Sun Servers, and such. But I knew python and django would be a better fit for this particular app, but the boss wouldnt listen. So we had 10 Developers working on the Java version (Including me) and over 3 months we got it about 85% done, though it had no unit tests. During the same three months, I worked on my own time after work and basically had no life for the whole time, I was able to get the web app 100% complete with unit tests. That convinced my boss that Django was a good fit. The site is an internal app that I cannot give access to (And I actually had to get permission to give what info I have), but I can say that Django is a suitable framework for what you are looking for.

Christ! 10 developers and no unit test!? Someone should remind them that you don't write unit tests for your bosses pleasure but for your own sanity and productivity.

I know that this quote is totally unscientific since Dj, as he says, can't back it up but it's a story interesting enough.

Related posts