165 karma · joined September 5, 2007
That being said, I think it is much easier for a coder to pick up on what is important for designers than vice versa.
If he wants to build something a bit bigger, and actually maintain it and grow it over time (e.g. cabinets for his kitchen), he would be wiser to spend time standardizing the parts and dimensions so that he can buy in bulk and speed production time (roll your own framework), or buy a pre-built set of cabinets and customize them to his kitchen and desired layout (existing framework).
Django provides a very clean layer on top of the database, and a great approach to structuring a system (apps, included urls.py, template dirs, templatetags, middleware). As with anything, though, the more complex the task, the more you need to be aware of what it is doing under the hood. Understanding when Django does lazy queries, where things are processed, etc. is very important.
It isn't intentional. When the billing has to cross between companies, and detailed requirements have to be agreed upon by multiple layers, the response time just can't be there.
Of course, hiring the right developers who can handle a large site efficiently is an equally frustrating challenge..
A big plus is being a unix nerd.
If you use python, and don't mind burning hours trying to just get your environment up, but really want solaris and their nas storage (which is really nice), this is a good option. However, there are alot of really cheap ubuntu/xen based vps's out there that are Really affordable and ready to take on your application in its early days. From experience i would recommend that for python developers.
stuff like code folding and automagical code generation encourage all the wrong habits. Simple, readable, and reused code is "tight".
at home its similar, but xfce4 terminals and pidgin on xubuntu.