Just finished reading So Good They Can’t Ignore You by Cal Newport, and his career advice mostly lines up with my personal experience.

The book’s advice for finding work that you love is to build up skills through years of *deliberate practice*, until your skills are rare and valuable enough to afford you control over your work. Being good at something and having connections will give you more opportunities and make your work feel more meaningful.

It tries to debunk the idea that boldly following your passions will lead to satisfying work. That approach won’t work if your skills aren’t valuable enough to support you, or earn you enough autonomy to enjoy your work.

“Working right matters more than finding the right work”, as the author puts it. The most interesting and rewarding work lies at the cutting edge of your field, where there’s room for new innovations, and plenty of consumers looking for those innovations. But to get there you need to have a strong knowledge of what you’re building upon, and you’ll need to be able to specialize in a small area that few others do.

Anyone who follows the indie game development scene will know how many new developers fail to make a living off of their passion, because they jump on the bandwagon without enough experience, or with unreasonably high expectations.

In my case, I didn’t consider doing game development full time until I was consistently making good money off of it, and it took me a long time to get there. Before that I spent a lifetime on learning how to draw, 7 years playing around with Flash and animations, and 4 years getting a software engineering degree – and not getting paid for any of that, but instead gaining skills and reputation. At first the effort wasn’t deliberate – game development was only a hobby – but after highschool I became more serious about looking at career options, and started measuring my progress and setting goals.

As I’ve learned recently, the most useful skills were often the ones that were the toughest to learn. I didn’t endure through University because I enjoyed learning about design patterns or project management, or because programming was my “passion”; I did it because I wanted some valuable skills which would make me a better game developer, or at least get me some other job if that path didn’t work out.
(Though I did begin to enjoy University once I gained control over my 4th year projects, which was only allowed because I had plenty of game dev experience by then.)

For a while, I became complacent with developing medium-sized web games, and stopped making an effort to improve my skills, opting to stick to what I knew and what was easy for me. Luckily, the market for web games started to shrink, and I was forced to look at the long-term viability of my career. I started looking at developing games for other platforms, including mobile devices and Steam, and although the process of adapting was difficult, I’ve gained a ton of valuable experience as a result, and feel more confident than ever. I’ve begun to make an effort to network with other game developers, to do more research on current market trends, and read boring textbooks. Most people never see the work that goes on behind the scenes.

Anyway, I think the main message to take away is that if you’re comfortable with the work you’re doing, that means you’re not challenging yourself enough, and you probably won’t get to where the most satisfying jobs are at. You should always take time off from being productive and instead squeeze in some time for research and practice, and concentrate more on what you can offer to the world, rather than what the world can offer to you.

Anyway, enough ranting from me.