53 karma · joined June 26, 2007
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!
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.
However, we are planning on selling the desktop version traditionally, and since it is more straightforward to develop, we decided to do things backwards and launch our Web 2.0 application as a desktop application first of all.
If you want to get info when the web version is done, add yourself here: http://www.ingolingo.com/lists/
I'd appreciate some honest criticism - what you like and what you don't like. This is the first draft, and I realize there is still a long way to go before getting it perfect!
Thanks! Mark.