I've worked in a place like this, and quit after little less than a year. They don't tell you upfront about all their crazy legacy software. The database is the Api for their applications, and the IT department gets to decide that you have to use Windows for development. The salary is average. My advice is to not take a job outside the software industry . I've never seen a place that was not broken.
I use the trackpoint exclusively, so I always buy a Lenovo without a touchpad. It's much better in my opinion, because you never have to move your hands away from the keyboard position.
Sad to hear that. I still remember applying for setting up my open source project on Sourceforge. My project eventually had 160.000 downloads from Sourceforge. Back in the days Sourceforge was immensely helpful for managing and distributing open source software.
I've used a couple of the django-heroku clones, Djangy, Gondor and Ep.io. Djangy is no more. Gondor is nice but lacking critical features (background jobs, caching... etc.), and generally seems like a sideshow to their consulting business. ep.io is ahead in features and quality so far. I have not tried DjangoZoom, as I was a little bit annoyed that they required me to pay for beeing in their beta test program.
Back in the days I also managed to write a bootloader and handle interrupts from the keyboard. I found GeekOS to be a great source to learn from. I even contributed a patch. http://code.google.com/p/geekos/
Yep, I agree. Tastypie has a steeper learning curve, due to beeing more flexible. When I used Piston, jespern was not actively maintaining it, but using a private branch for bitbucket.
Yes, it does. I just think imposing prod. setup testing on your dev env., is the wrong place to do it. For many django apps, I've been able to use testserver, staticserve, dummycaching, synchrounous Celery tasks, etc for development. Just configs that works on checkout. If I need a special database, or something with a non standard interface I add only that to my setup.
You are right. My bad. My point though, was that I think the cost in terms of complexity of using Vagrant for development is too high. The goal of having your dev environment match your prod. env. is not the right approach in my opinion. This the role of the staging environment.
I have used both Piston and Tastypie, and by far prefer Tastypie. Tastypie is actively maintained and super flexible. It gets you working out of the box with the django ORM, but also has the hooks to plug in everything you want.
You should just go ahead and build it anyway. If you do a good job, competition won't matter that much. I have customers in a space with thousands of competitors (event management software).
My first full time software job, was writing C for PSION Workabout terminals. They had 2MB ram and their own custom plib for system access that ran more efficient than using clib functions.
Same here... Just a week ago, I spent the whole night looking at code trying to find out how some mysterious data loss had occurred. Needless to say, I had been to bed half an hour before it hit me what had happened. I instantly got up and fetched my laptop to confirm that was indeed the case.
I think you are right, about letting go of all assumptions, and that helps you find the edge cases.
I just requested a refund for MEAP for "Secrets of the JavaScript Ninja", that I ordered almost three years ago. I didn't expect it to take that long...