I wrote my app in Python/Django. My reasons were short:
1. I wanted to learn python, but was not really interested in ruby
2. Rails is too hyped. The problem here is that people pigeonhole you when they hear that you are a rails developer. If someone ever came to me and told me he was a rails developer, I would immediately perceive this guy as someone who jumps on technology bandwagons. The type of guy who listens to top40 charts.
3. Django just had a way better argument when it came to performance
and the most important reason of all
4. When I created a new Django project, it just created 3 files. Rails (when I tried it) created a bunch of folders and files. People have to understand simplicity in all its facets to be effective programmers, in my opinion!
I believe the problem here is just microfocus. When people focus too much on one thing, they tend not to take a step back every now and then to see if things are still the same as when you started. Let's say I want to start a business in china making valves for microturbines. I spend half a year and progress is very slow. It's time to realise that things are bad, take a step back and review the process. If things are hard, you are doing something wrong.
Sometimes it's neccesary to work hard. But sometimes is not a year. One has to take life in 6 month chunks, and you only have about 140 of those. You lose one, you will never get it back. A year is two of those chunks. It's too much time to be unhappy in.
I'm one of the fastest developers I know because I was taught the technique - when things start going slow, stop, zoom out and analyse the reason why it's going slow. Then go back in, but approach things differently. This time you want to maintain the quality of work, but reduce the time spent on it. It's not difficult to optimize that.
BTW, this'll be familiar to anyone that's learned a musical instrument. The way you get speed in music is to slow down the tempo until it's at a level where you can easily play the piece (with a new piece, this is often 1/4 or less of actual speed). Then you work on control and rhythm only, until you've got it perfect. Then gradually bump up the tempo for as long as you can maintain control. If you start getting sloppy, slow it down and practice more at the lesser tempo. Eventually, you'll be able to play it perfectly at tempo, with a good reserve if you wanna speed it up for effect.
I was in the same boat and hired somebody. It wasn't cheap for me, but now that the dollar has fallen it might be cheap for you to hire someone in the U.S.
Thanks for the criticism. Well, just try it out. 30 words is just two lessons a day - I think people underestimate the power of repetition in learning. 30 words is easy if you do two lessons a day. Yes, the text stuff is not completely done yet, it still references parts that are not online yet. That's why we have the 404s still.
No problem. I did later try it out, and it looks like those 6 languages are all that's offered; unfortunately, the language I'm learning right now (and the previous one) are not among them. Maybe I'll try back later.
Right now I've got a stack of flash cards I carry with me everywhere. Whenever I'm not being productive at work, I pull them out and flip through them for a few minutes, sometimes many times a day. If I can learn (and remember) 5 new words, it's a good day. So I'm still skeptical if the trick is simply "repetition".
Well, try this. Click on the chinese course and spend 1 hour on it. You should be able to do 2 lessons in that time. Write down all 30 words you learnt on a piece of paper. Sleep on it, wake up the next morning and read the paper and see how many you still remember. It won't be 30, but I think it will be more than 5. Don't forget to click the button to view the pictures for the words.
1. I wanted to learn python, but was not really interested in ruby 2. Rails is too hyped. The problem here is that people pigeonhole you when they hear that you are a rails developer. If someone ever came to me and told me he was a rails developer, I would immediately perceive this guy as someone who jumps on technology bandwagons. The type of guy who listens to top40 charts. 3. Django just had a way better argument when it came to performance
and the most important reason of all
4. When I created a new Django project, it just created 3 files. Rails (when I tried it) created a bunch of folders and files. People have to understand simplicity in all its facets to be effective programmers, in my opinion!