“The main effect of automation in the computer era is not that it destroys blue-collar jobs but that it destroys any job that can be reduced to a routine.”
“The main effect of automation in the computer era is not that it destroys blue-collar jobs but that it destroys any job that can be reduced to a routine.”
“What makes SaaS so special, when architected correctly, is that the addition of users and customers to the application over time will make the experience better for everyone involved.”
“…it is simply not possible to create excellent, detailed icons which can be arbitrarily scaled to very small dimensions while preserving clarity. Small icons are caricatures: they exaggerate some features, drop others and align shapes to a sharp grid. Even if all icons could be executed as vectors, the largest size would never scale down well.”
Always enjoy reading recaps on a design process. I particularly liked this:
We didn’t have beta testers sign NDAs or demand first-borns to get access to the early builds. How on earth did we keep something under wraps for so long?
We asked people politely not to share it with the world. It’s really not that hard. Don’t send betas to douchebags. Politely ask people not to blog about it. Done.

Le’beast
At GitHub, we think that sharing code should be as simple as possible. That’s why we created GitHub for Mac.
And I now have new perspective on ideas, the madness and sustainability.
“I was focused on trying to make the usability of editing data as easy and functional as it could be; Mint was focused on making it so you never had to do that at all. Their approach completely kicked our approach’s ass.”
Marc Hedlund – Why Wesabe Lost to Mint
If you’re getting Ruby Gem deprecation warnings (eg: after switching to Ruby 1.9.2) you can most likely fix it by doing the following.
On the subject of Sass, I noticed a pesky warning when running the sass watch command.
Warning: Unable to load CarbonCore. FSEvents will be unavailable.
Turns out if you’re getting this error it means your Terminal is actively polling a sass directory for changes rather than natively listening for changes. The former method being resource intensive. Not cool.
My attempts at getting rid of this error lead me on a labyrinth of ‘Stack Overflow’ suggestions which included installing RubyCocoa, which I found out wasn’t compatible with Ruby 1.9.2, but which then also failed to compile with Ruby 1.8.7 despite clear examples it should work! etc etc.
In the end the solution was simple.
gem install rb-fsevent
gem install fssm
Found in a comment the bottom of this page.
Rails 3.1 integrates CoffeeScript and Sass out of the box via the new asset pipeline. Which is super! Unfortunately I don’t work on Rails all the time. Most of our client projects are running swimmingly on Expression Engine.
With the official Rails 3.1 release imminent, I pondered, searched and found both a Sass Textmate Bundle and a CoffeeScript Textmate Bundle.
Bonus: I noticed this in a recent Railscast’s video, Missing Drawer a better sidebar for Textmate.
New toys ftw!
Note to self.
Super!