Sitemap
Press enter or click to view image in full size

Career tips for freelance developers — a brief interview with @iosengineer

5 min readOct 21, 2014

--

A little over a month ago, I received an email from a reader of my blog asking for advice on pursuing a career in iOS and freelance development. What started out as an email response turned into an introspective pondering that the reader was quite thankful for, so I decided to share the questions and answers publicly, to give other seekers a helping hand. Kudos to Randel for reaching out and asking for the advice in the first place.

How did you get your first iOS development job?

My first iOS job was actually my own project. It took a HEAP of time and money to make and ended up as a big-time flop on the App Store. On the upside, I taught myself Objective-C and Cocoa, which was vital to getting into the mobile development industry.

My first actual paid work was a startup that wanted some revolutionary bleeding-edge stuff put into an app. I was intellectually capable and experienced enough to do it but I was totally green in business, so that ended up tanking badly.

The first successful gig I had was making a rapid prototype app for a medical company. I studied the HIG (Human Interface Guide) hard and created an interface that impressed the board of a large Sydney hospital — it won my client the contract.

Finding these roles was a matter of asking around, looking on job sites and having a resume with good attention to detail (at the time). These days, it depends on what you’re seeking. I don’t seek employment. I seek jobs. So I have samples of work on my site and source code on GitHub for open review. Most of my work comes from word-of-mouth and networking but I’m also looking into advertising.

Get Adam Iredale’s stories in your inbox

Join Medium for free to get updates from this writer.

iOS wasn’t my first programming role, however. Programming from an early age, I pursued it through school and then university, coming out with a Bachelor of Science in Information and Communication Science. While a degree isn’t essential to being a programmer, the best programmers I know were formally trained first. Having said that, I also know a few formally trained programmers who should have applied for a job at the zoo. As a monkey.

Do you have any advice for freelance developers?

LOADS. Here are my top three:

  1. As a priority, get a good lawyer to draft your standard terms agreement. It cost me only $750 and it’s the best $750 I’ve ever spent. You use it every time there’s work and it keeps you safe and clear about your rights. Along this vein, also look at getting Professional Indemnity Insurance as a priority. Nothing eases your nerves and allows you to work in your own style like knowing that if worst comes to worst, you’re safe if you’re sued. Also on this, until you’re up to speed with legalese, pass all contracts through your lawyer to advise you before you sign them. All of these items I learnt from the hard way and was burned.
  2. Get on Twitter and follow me and anyone else who will keep you in the loop for what’s going on in the iOS and Cocoa development community. Every developer worth their salt is involved in that community via Twitter. Support is awesome and believe me, you’ll need it. In addition, the open source contributors on there are always happy to help with their stuff.
  3. If you can, attend the CocoaHeads meet nearest you. Having a steady flow of interesting work (or any work for that matter) and having friends to help you out comes down to good networking. I’ve been a regular for a couple of years now and I’ve even presented a few times. The most important part is simply being there. You’ll get the most up-to-date information and support and there are like-minded folks there who can share your burdens (maybe over a beer). In addition, when you meet someone IRL, they’re more likely to freely engage with you on Twitter.

What are the most important skills should a developer have?

Tough one. Ok, we’ll go with three again for consistency.

  1. The desire/passion/focus/intent/whatever to become better with each passing moment of their lives. Whether that’s more efficient at coding, better at estimates, better at networking, better at social interaction or better at thinking, they have to want to be better. It’s in their blood. It’s all connected.
  2. Balance. Learn that every single thing you do is a balancing act. Whether it’s a balance between time and cost or between CPU cycles and development time, it’s all a big balancing act. Learn to balance things. Step back and see the big picture. There are always trade offs and nothing will ever be perfect. On the flip side, hacking stuff together without thinking will always result in bad days. Which brings me to number 3.
  3. Excellent development starts on paper. Now, I’m no purist. I keep an open mind and I use prototyping apps of all kinds and am always reading more and learning more about better (see point 1) ways to do things, but coding things straight from your head should never be a thing. The mind is too fluid a place to construct lasting things. Paper and pencil first. Design it. See how it should work, feel, flow etc. There was a great session at WWDC this year on prototyping and I highly recommend it. It’s called “Fake It Til You Make It”. Once you have the design, the data diagrams, the lists of features (and those rejected for now) etc, then you can start to code things. Having said that, if you want to play in a playground with some code that’s fine — just don’t make a serious app that way.

Many of the points covered here are just the tip of the iceberg and this is far from my last post on the matter, so if you’d like to get in touch with more specific questions, come tweet at me or drop by applifebalance.com.

--

--

Adam Iredale
Adam Iredale

Written by Adam Iredale

iOS Professional, Meditator, Tea Enthusiast, PWNc