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.
For anyone who's interested, we recently launched a new site to help people find office space for lease in portland. It's a rails app, with a lot of coffeescript and scss and has really helped refine a lot of the ideas I have about structuring front end code.
One of the main attractions of freelancing is the mobility. You can - theoretically - work from anywhere.
I was recently lured back to the states to work for a startup in Seattle. But before that, I spent over a year living and traveling in Mexico while working as a web developer for clients in the US.
When I first contemplated taking the leap, I was surprised to find that there wasn’t much practical info to help web developers and other freelancers who want to travel the world. The information that I did find was mostly BS.
So, here you go world. Here’s how to become a globe-trotting freelancer in 28 easy steps:
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."
I'm a rails developer and a lot of my work has to do with building out the UI. Over the past few years I've developed a number of best practices that have really helped me to build solid, maintainable front ends for fairly complicated web apps.
I believe that most rails developers could improve the quality of their front and builds by adopting a few of these suggestions.
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)
Fortunately, postgres provides some nice fuzzy text search features out of the box. And they're super easy to use.
Ok...If you really love SQL, this is not the article for you. I'm going to share a little trick I've learned that will let you do really complex queries without writing a lick of SQL.
Now, mongo isn't the solution to every problem. But for some things, like action tracking, it is close to perfect.
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?
So I have a client who needed a google voice widget embedded in their site.
If you're not familiar with it, it's a little widget that your site's visitors can use to call you.
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.
I recently needed to create arched text in an application that uses Cairo. Unfortunately, Cairo doesn't support warping text out of the box.