The Startup Teardown is a neat video podcast where the host reviews a startup's sales pages and onboarding experience and gives helpful advice.
What's the use in writing great code if nobody uses it? In this talk at Cascadia Ruby I demonstrate a simple method for usability testing that engineers can and should use:
If you're interested in machine learning and Ruby, you'll probably like this talk I gave at Pivotal Labs in San Francisco:
I wasn't an expat freelancer for the lifestyle, the adventure, or the romance. No sir. I was in it for the taxes. Well not really. But here's something you may not have thought about: Expat freelancers can save a ton of money on taxes.
When building out officespace.com, one of the best decisions we made was using an image server for all of our resizing. It's really nice to be able to tweak your image size on the fly, rather than on upload.
One of the main attractions of freelancing is the mobility. You can - theoretically - work from anywhere.
Based on a reader comment about the previous post, I put together a sample rails app showing how I structure my front end code.
Most front end code sucks. You know the situation. You start out with the best intentions every time, but every time you wind up with something "less than maintainable."
On my latest project, one of our guiding principles was to keep then number of moving parts to a minimum. (That sphinx/solr server your running is just one more server that can go down)
So you're given an archive containing 10,000,000 .ttf files, most of which are named things like "bs019dfk.ttf". How do you extract human readable names from these things?
Yesterday I was working on a project, and found myself needing to create a bunch of color swatches. CSS wasn't an option. No. They had to be little 16x16 images.
John Nunemaker posted a great article on using uploadify with rails.
I recently needed to create arched text in an application that uses Cairo. Unfortunately, Cairo doesn't support warping text out of the box.