niels

Twitter is they.

Which also is the reason you can only have 5000 friends on FB. If you had a million friends, you'd probably touch all their servers for one request.

Yep, so basically one request can touch hundreds of servers. It's basically the opposite approach of Twitter. They aggregate the graphs on write.

One really important point, that is not mentioned, is that even if a great app exists, you will not be able to make any money off it. That's why it makes sense to build and own the app your self.

guestlistapp looks like a really great app. Both design and usability. Well done.

I'd love to try rescuetime, but their linux client was working last time I tried. Don't remember what the issue was exactly though.

OK, I may have overstated my opinion on this. You can probably say something about people using Myers-Briggs. However I feel weird beeing categorized like that. I am beeing typed as an introvert but I don't see myself as beeing introverted at all. This stuff is too vague and subjective for me to have any meaning (I guess you are gonna type me based on this??).

I didn't answer the poll because I don't believe in Myers-Briggs Type Indicators.

No, because accessing a object property requires a hash table lookup.

It uses webfonts: http://webfonts.info

vocal trance http://di.fm/vocaltrance

I've been curious about some of the tools behind Google's javascript power. The Closure Library coupled with the compiler looks really useful for creating complex and fast web apps.

lighthouse ( http://www.lighthouseapp.com )

Not to forget daemontools.

Yes, you can use Django trunk if you do like this:

http://lethain.com/entry/2009/mar/05/deploying-django-spring...

Django Debug Toolbar is a must use for Django development. I hope it becomes a contrib app at some point.

I really like how it enables you to update the page efficiently after the page has been rendered.

The easiest way is to join a sailing club, if there is one nearby. They often have a sailing school and boats you can borrow. Alternatively you can buy a cheap dinghy.

Basically the async mechanism allows you to handle a lot more concurrent connections. This is handy if you do comet style applications where you need persistent connections to the clients.

This is not some new insight pg just came up with. In fact it is pretty common knowledge, as Joel and many other has written countless times before, that interruptions are costly for software developers. Slapping new words on a well known and well understood problem, is not insightful.

What I meant exactly is, give an estimate and an hour quote. Let the client know that if you complete the project in less time, you will charge less and vice versa. I've found that in all projects specs change and things take less or more time than estimated. Nothing sucks more than working free because you underestimated a task. Also if you have a fixed price, you will invariantly be motivated to take the quick and dirty solutions everytime. This will not lead to success for the project.

In my experience quoting per job will lead to a very bad experience for either you or the customer, and possibly both. By quoting per hour, you will be payed for your work and the customer will only pay for the work done.

I had exactly the same idea. This is a great post. Ohh.. how we all have been there.

I think they are referring to html5 web workers http://www.whatwg.org/specs/web-workers/current-work/

This is clearly the best Human Computer Interaction article I've ever read. Great stuff. Thanks.

I use App Engine because of its simplicity and ease of deployment. I include Django trunk in my sources, so I am not really missing anything for regular web apps.

I didn't notice this trend but incidentally I just bought a sailboat and took sailing classes. And sailing is awesome in more ways than I can count.

I personally prefer the simplicity of App Engine, for the types of apps that fits in that space. As I heard they have plans to support other languages later on. They are constantly improving the service.