B!? Links

Of users naming a single preferred toolkit, Ruby-GNOME2 and Shoes were chosen by 26%, wxRuby by 17% and RubyCocoa 11%; no other toolkit received more than 10%.

Other Things Software Architects Should Know

Interface Builder for Cappuccino

Interface Builder Plugin for Cocoa on Mac OS X

Diff, Match and Patch libraries for Plain Text

1. Pick good cofounders.
2. Launch fast.
3. Let your idea evolve.
4. Understand your users.
5. Better to make a few users love you than a lot ambivalent.
6. Offer surprisingly good customer service.
7. You make what you measure.
8. Spend little.
9. Get ramen profitable.
10. Avoid distractions.
11. Don’t get demoralized.
12. Don’t give up.
13. Deals fall through.

The first thing you need to know is that learning how to develop applications for a mobile device isn’t easy. But it’s worth the effort, ask any seasoned iPhone developer about seeing their work run on the device for the first time: it’s fricken’ amazing.

A Ruby-powered JavaScript dependency library from 37signals

A better way to think of a manager is as a servant, like an editor or a personal assistant. Everyone wants to be effective; a manager’s job is to do everything they can to make that happen. The ideal manager is someone everyone would want to have.

You have to skate a pretty thin line between security and usability some times. Internet users have literally hundreds of passwords to remember for the sites they use on a daily basis and while I might not mind so much if my youtube login was compromised, my bank account being hacked would be a serious hassle. So, how do we design a security system that protects the user’s information while keeping it useful to use?