<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adam Iredale on Medium]]></title>
        <description><![CDATA[Stories by Adam Iredale on Medium]]></description>
        <link>https://medium.com/@iosengineer?source=rss-13ae32a8b7d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*1EkXz0lsFDt5DA_t.jpeg</url>
            <title>Stories by Adam Iredale on Medium</title>
            <link>https://medium.com/@iosengineer?source=rss-13ae32a8b7d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:53:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@iosengineer/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Career tips for freelance developers — a brief interview with @iosengineer]]></title>
            <link>https://medium.com/@iosengineer/career-tips-for-freelance-developers-a-brief-interview-with-iosengineer-4c0f2c298542?source=rss-13ae32a8b7d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c0f2c298542</guid>
            <dc:creator><![CDATA[Adam Iredale]]></dc:creator>
            <pubDate>Tue, 21 Oct 2014 23:46:00 GMT</pubDate>
            <atom:updated>2014-10-21T23:46:00.931Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJrvcjpj18MWjguRynf5ZQ.jpeg" /></figure><p>A little over a month ago, I received an email from a reader of <a href="http://applifebalance.com/blog">my blog</a> 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.</p><blockquote>How did you get your first iOS development job?</blockquote><p>My first iOS job was actually <a href="http://applifebalance.com/client/">my own project</a>. 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.</p><p>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.</p><p>The first successful gig I had was making a rapid prototype app for a medical company. I studied the <a href="https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/">HIG (Human Interface Guide)</a> hard and created an interface that impressed the board of a large Sydney hospital — it won my client the contract.</p><p>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.</p><p>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.</p><blockquote>Do you have any advice for freelance developers?</blockquote><p>LOADS. Here are my top three:</p><ol><li>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.</li><li>Get on Twitter and <a href="https://twitter.com/iosengineer">follow me</a> 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.</li><li>If you can, attend the <a href="http://cocoaheads.org/">CocoaHeads</a> 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.</li></ol><blockquote>What are the most important skills should a developer have?</blockquote><p>Tough one. Ok, we’ll go with three again for consistency.</p><ol><li>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.</li><li>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.</li><li>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 <a href="https://developer.apple.com/videos/wwdc/2014/?include=223#223">“Fake It Til You Make It”</a>. 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.</li></ol><p>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, <a href="https://twitter.com/iosengineer">come tweet at me</a> or drop by <a href="http://applifebalance.com/">applifebalance.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c0f2c298542" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with iOS development in the age of Swift]]></title>
            <link>https://medium.com/@iosengineer/getting-started-with-ios-development-in-the-age-of-swift-aca8a437f6cb?source=rss-13ae32a8b7d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/aca8a437f6cb</guid>
            <dc:creator><![CDATA[Adam Iredale]]></dc:creator>
            <pubDate>Mon, 14 Jul 2014 04:31:37 GMT</pubDate>
            <atom:updated>2014-10-16T14:26:26.925Z</atom:updated>
            <content:encoded><![CDATA[<h4>A brief recommendation on how to start developing for iOS today</h4><h3>Which language should I learn? Objective-C or Swift?</h3><p>The short answer is: both. Apple’s new language is in headlines and clickbait everywhere in the iOS and OS X development world today — but don’t be fooled. It will be many moons before Swift is fully integrated into the developer workflow and Objective-C is going nowhere fast. I recommend that budding iOS developers take their first steps in Objective-C and here’s a few reasons why:</p><h4>Apple’s frameworks are built in Objective-C and C</h4><p>They’ll likely start to transition everyone over to Swift gradually but for the main part, they’re in the same boat that we’re in. A little over a month ago, only 200 developers were actively using Swift. Apple kept Swift close to their chests as they built it up over a period of 4 years. Up until the Keynote this year, all but 200 of Apple’s internal developers apparently had no clue about it either. Objective-C is robust, and has stood the test of over 20 years of use.</p><h4>Swift is still in beta and is subject to change</h4><p>Xcode 6 beta 3 made some significant changes to the way that arrays and dictionaries work and broke a lot of prior code. Learning a language is hard enough without having to learn what is and isn’t your fault. Swift will continue to make breaking changes until at least version 1.0 in a few months. Any oddity in Objective-C is generally widely known and documented.</p><h4>Swift was designed for interoperability with Objective-C and uses the same runtime</h4><p>Most things you learn in Objective-C can be mapped to a conceptual understanding in Swift, and as most of the iOS and OS X developers have been writing in Objective-C up until this point, some concepts are easier to understand if you first know Objective-C.</p><h4>Objective-C material is everywhere</h4><p>Objective-C tutorials and examples permeate the web. Books on iOS development are all (at this stage) written in Objective-C. <a href="http://stackoverflow.com/">Stack Overflow</a>, <a href="http://www.raywenderlich.com/">Ray Wenderlich</a> and countless other tutorial sites are filled with iOS tutorials, examples and workarounds — all in Objective-C. It’s been used for over 20 years! As you learn how to develop for iOS and run into problems or have questions, the answers you seek will still (for a long while) be written in Objective-C.</p><h4>Legacy code takes a long time to die</h4><p>Even when Swift has been fully embraced by the developer community in their daily grind, there are still going to be billions and billions of lines of legacy code written in Objective-C. You can’t fix or convert what you don’t understand. In addition, there are <a href="http://cocoapods.org/">thousands of third party libraries</a> and powerful tools that (still) use Objective-C, so an understanding of how these work is vital for adopting them with confidence.</p><blockquote>By starting with Objective-C, you will build a firm foundation for iOS development and learn a lot of the Cocoa frameworks that Swift also uses.</blockquote><h3>Learning Objective-C</h3><h4>From Apple with love</h4><p>The best place to begin is at the source: Apple’s <a href="https://developer.apple.com/library/ios/navigation/">iOS Developer Library</a>. There are a tonne of guides, documentation and sample code here. In order to point you in the right direction, I recommend starting with these:</p><ol><li><a href="https://developer.apple.com/library/ios/referencelibrary/GettingStarted/RoadMapiOS/index.html#//apple_ref/doc/uid/TP40011343">Start Developing iOS Apps Today</a></li><li><a href="https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/Introduction/Introduction.html#//apple_ref/doc/uid/TP40011210-CH1-SW1">Programming with Objective-C</a></li><li><a href="https://developer.apple.com/library/ios/documentation/General/Conceptual/CocoaEncyclopedia/Introduction/Introduction.html#//apple_ref/doc/uid/TP40010810">Concepts in Objective-C Programming</a></li><li><a href="https://developer.apple.com/library/ios/releasenotes/ObjectiveC/ModernizationObjC/AdoptingModernObjective-C/AdoptingModernObjective-C.html#//apple_ref/doc/uid/TP40014150">Adopting Modern Objective-C</a></li><li><a href="https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/CodingGuidelines/CodingGuidelines.html#//apple_ref/doc/uid/10000146i">Coding Guidelines for Cocoa</a></li><li><a href="https://developer.apple.com/library/ios/documentation/Cocoa/Reference/Foundation/ObjC_classic/_index.html#//apple_ref/doc/uid/20001091">Foundation Framework Reference</a></li></ol><p>You’ll also want to check out the <a href="https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/index.html#//apple_ref/doc/uid/TP40006556">iOS Human Interface Guidelines</a>, commonly known by developers as “the HIG”. I quite often <a href="https://twitter.com/iosengineer">tweet</a> about #badUX and #livebythehig and this is the reference manual to which I refer. The sheer number of horrible apps that exist tell me that not enough developers are taking the time and care to read and apply the design guidelines in this excellent manual.</p><h4>Other helpful resources</h4><p>Luca Bernardi and Alberto De Bortoli have just released <a href="https://github.com/objc-zen/objc-zen-book">an excellent free style guide for writing beautiful Objective-C (highly recommended)</a>.</p><p><a href="http://www.raywenderlich.com/">Ray Wenderlich</a> is an excellent resource for learning iOS development, and I’d recommend that you at least buy the “iOS 7 by tutorials” book and consume it (and iOS 8, once it’s ready). Once you understand the basics of Objective-C, this particular guide will help you understand how to use it with outstanding easy-to-read tutorials. In addition, Ray’s site is so chock-full of tutorials and guides that you may find everything you need there (so do all the freely provided ones first and consider whether or not a subscription would benefit you).</p><p>If video is your thing then you should check out <a href="http://nsscreencast.com/">NSScreencast</a>. It offers subscribers (and occasionally has some free videos too) weekly, highly-polished walkthroughs of many areas of development for iOS, delivered as screencasts. It covers tools, techniques, frameworks and a lot more. Well worth a look.</p><h3>Next up, Swift</h3><p>Don’t rush into learning Swift. A good understanding of Objective-C and iOS development in general is far more important at this point than Swift. It is still in flux and many errors that you will encounter may not be your fault at all, which is a horrible learning experience. With that in mind, here is the order that I recommend people use to learn Swift with the least amount of hair-pulling and screaming:</p><h4>Videos</h4><p>Visit <a href="https://developer.apple.com/videos/wwdc/2014/">WWDC 2014</a>&#39;s video page and watch these sessions in order:</p><ol><li>402 — Introduction to Swift</li><li>403 — Intermediate Swift</li><li>404 — Advanced Swift</li><li>406 — Integrating Swift with Objective-C</li><li>407 — Swift Interoperability In Depth</li><li>408 — Swift Playgrounds</li><li>409 — Introduction to LLDB and the Swift REPL</li><li>410 — Advanced Swift Debugging in LLDB</li></ol><p>There is also a great demo of some of the powerful features of Swift and Playgrounds given in the <em>Platforms State of the Union</em> video.</p><p>Don’t worry if you don’t pick up all the details. The videos will lay the groundwork for your documentation ingestion. Once you’ve watched the videos, you’ll be able to absorb the documentation much faster than I did (I read the docs first over several mind-bloating days).</p><h4>Documentation</h4><p>Parts of the iOS 8 <a href="https://developer.apple.com/library/prerelease/ios/navigation/index.html">pre-release documentation</a> have been released as <a href="https://itunes.apple.com/au/book/swift-programming-language/id881256329?mt=11&amp;uo=4&amp;at=10lMGL">two</a> <a href="https://itunes.apple.com/au/book/using-swift-cocoa-objective/id888894773?mt=11&amp;uo=4&amp;at=10lMGL">free</a> iBooks on iTunes, but either source is fine to use. I recommend the former (also available from the Help menu in Xcode 6), as it opens easily as a Playground where available.</p><p>You’ll want to read:</p><ol><li>The Swift Programming Language*</li><li>Using Swift with Cocoa and Objective-C</li><li>Swift Standard Library Reference</li></ol><p>*<em>When reading the Swift Programming Language, read it in the following order: Language Reference, Language Guide, Welcome. This order is not intuitive, but it will allow fastest absorption. The reference quickly covers the important points about the language, the guide covers the language with worked examples and the welcome contains an interactive Playground that you can use to test your understanding.</em></p><h4>Moving forwards by looking backwards</h4><p>After all this learning, you may want to go back to the examples that you’ve built in Objective-C and consider how they would be best implemented in Swift. A simple port might be your first step, but also consider that Swift is very different from Objective-C and may have new tools that would solve the problems in a different way. We’re all learning at this stage, so experiment often, and tell others your findings.</p><p>With that, I leave you with my wish for you of only the Swiftest of experiences, developing Objectively great apps. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aca8a437f6cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to deal with work drought]]></title>
            <link>https://medium.com/@iosengineer/how-to-deal-with-work-drought-baeee89a0f7f?source=rss-13ae32a8b7d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/baeee89a0f7f</guid>
            <dc:creator><![CDATA[Adam Iredale]]></dc:creator>
            <pubDate>Thu, 10 Jul 2014 06:00:51 GMT</pubDate>
            <atom:updated>2014-07-10T06:00:51.267Z</atom:updated>
            <content:encoded><![CDATA[<h4>Dealing with the ebb part — of the ebbs and flows of being an independent consultant</h4><p>Work drought is an understood risk of working as an independent consultant. Ideally, you will have a buffer of money saved up for this eventuality and you can take a holiday while you wait for clients to sort out new project specifications, rack up adequate funding or come back from a holiday season. If this is the case, then great! You can take a much-needed restful break from the often intense work of running your own business. If not, don’t despair. As long as your industry is rich with potential work, all you have to do is put yourself in the right place at the right time to find it.</p><h3>Stay calm</h3><blockquote>“Desperation is a stinky cologne, John” — Super Troopers</blockquote><p>Although it’s important to be truthful with potential clients, there is such a thing as giving too much information. You may feel fear and panic in your gut, but you must maintain your professionalism. Professionals don’t beg. Running a business or company is hard work — especially if you’re just starting out. It’s quite common to go into debt (if you’re lucky) or run into periods where you wonder how you’re going to pay your bills. These times can act as the motivation that you need to do what needs to be done or to make sacrifices needed to survive. They can teach you a lot about yourself. About how you behave under pressure. About what your true priorities in life are.</p><p>Despite this tumultuous emotional period in your life, you’ve got to keep all of that buttoned down and locked away under the hood of professionalism. When you write to potential clients about work or meet them in person, it’s vital to be able to step away from the chaos that may be raging inside you and put on your game face. You’re representing your business now. This is your professional image. Cool, calm and collected. When people consult a professional, they want a professional experience — one that is full of confidence and product knowledge and wisdom from experience. If you’re going through emotional turmoil, this can undermine a lot of your confidence, so separation of business from yourself is important. Just because things may be tough right now, it doesn’t change the fact that you are a highly valuable industry professional. The alignment and timings of projects does not change that.</p><p>Because you have some available time during work drought (more on this later), it might be a good time to sit down and listen to what your mind and body tell you about how you deal with this kind of thing. I’m a big advocate of Vipassana or Mindfulness Meditation. It allows you to sit quietly (or walk if needed) and learn some profound, possibly life-changing things about yourself. All you have to do is listen to yourself openly. The reason I mention this is that there is no better way to stay calm than to actually <em>be</em> calm. Don’t bottle it up. Mindfulness can certainly help, but if that’s not your cup of hot beverage, you can try other activities such as Yoga or jogging or possibly even gaming. The bottom line is that the more calm and at peace you are, the clearer you will think and the better you will present to clients.</p><h3>Revise your finances</h3><p>One of the biggest sources of internal discomfort when dealing with work drought is fear of wolves. That is, how to keep them from the door. If you are not the one in your business or household who does the budget or worse yet, you don’t have a budget, now is a good time to become reacquainted with your balance sheet. Stop optional services if required, reduce budget categories and hold off on buying that new laptop. Your level of comfort and available funds will dictate the lengths you will go to in this area.</p><p>Once you’ve reviewed and possibly reduced your expenditures, you then need to see how long you can make what you have last. If you’re renting, as we are, this will likely be your largest single expense. A good rule of thumb is judging how long you can last without income by how many times you’ll be able to pay your rent. A buffer of one to three months expenses is ideal, but if you don’t have that, remember that the people you pay bills to are just people and can be reasoned with. They are often sympathetic and you may be able to get away with paying your bills late. It is best to contact them before defaulting, though and <strong>never</strong> default on a payment to the ATO without discussing it with them first.</p><p>There are a few different levels of desperation when in work drought, but these are mainly personal, based on your level of lifestyle comfort, and are judged by the sacrifices that you may have to make should things get so dire. Obviously the first things to go are optional purchases and one of the last is reconsidering where to live or perhaps temporarily becoming <em>*gasp*</em> an employee. The important thing to keep in mind is that absolutely none of this is the end of the world. With each stage of desperation, something that you value or cling to is targeted and it will either hold or dissolve, showing you what you really value in life. Eventually, the most valuable things to you become clear. These are the things you are not willing to negotiate on.</p><p>While you are in this drought, you must keep a regular eye on your bank balance. It’s pretty much the driving force and helps you decide when to alter your approach, lower your rates or consider other sacrifices.</p><h3>Publicly announce your availability</h3><p>No one is going to be able to give you work unless they know you need it. Publicly announcing your availability should be something you do as early as you can. If you know that your work pool is drying up or negotiations are taking too long or your spidey-senses are tingling, you should probably announce your availability. If you currently advertise, you might want to review your campaigns. If you don’t, you may want to consider looking into it.</p><p>I believe it’s important to be involved with your industry. I pride myself on being on the cutting edge of available technologies, but staying abreast of these things is a mammoth task, especially in an industry like mobile app development. You’re only one person, so your time is limited to the amount of time one mind can use. This is why there are industry groups. They’re out there for most consulting industries and locations. I attend <a href="http://sydneycocoaheads.com/">CocoaHeads Sydney</a> once a month. It’s invaluable for getting together with peers and like-minded individuals, learning industry developments, networking and finding work. So if you’re not hooked up with an industry group, find one and become involved. Let them know you’re available for work. CocoaHeads has a mailing list and they also have a short segment towards the end of the evening to allow those either looking for work or those who have jobs available to make announcements.</p><p>Another medium that plays a huge role in my industry is Twitter. I’m quite <a href="https://twitter.com/iosengineer">active on Twitter</a>. It’s an excellent medium that doesn’t bog you down with lengthy posts and forces content (the summary, at least) to be short and sweet. People actively involved in the industry community are often on Twitter. It’s how I get my breaking news and announcements and it’s a great way to announce availability, provided you acknowledge the peak times. For Twitter, and obviously, for local users, the best time to announce anything is between 1 and 3pm on weekdays. This is when people go to lunch and tend to check their social networks the most. When in work drought, I find that people in general don’t mind if you announce your availability once a day. Any more than that and you’ll probably start to lose followers for spamming.</p><h3>Contact past clients and peers</h3><p>Once you’ve announced your availability through your usual public channels (and perhaps considered other public channels too), it’s probably in your interest to contact companies that you’ve consulted with in the past to see if they have anything going on or about to be going on. Often, there are jobs in their pipeline that are waiting for the right conditions and you contacting them might just be those right conditions. This also applies to friends and peers in the industry. It’s common that at least a handful of peers are overladen and more than happy to buy some of your time to ease their load.</p><p>Now would be a good time to freshen up your Client Relationship Management system if you have one, or start looking into one if you haven’t. A spreadsheet is enough to get started, with columns for name, contact number, email address, last date of contact (rough) and notes on what you were last discussing or working on. It’s great for keeping continuity in discussions that may stop and start months apart. It helps you remember to ask clients about how their last <em>whatever</em> went. You should do that. It shows people that you care.</p><p>Another thing to remember is not to be afraid of actually speaking to people on the phone. Emails are usually enough to get in contact but these days telephone calls are rarer and tend to stick in people’s minds. If you’ve had a good experience with a client or peer in the past, a phone call will let them hear your voice and remind them of that positive experience. At the very least, it guarantees that you will be heard and not (in the case of the busier kinds of people) be buried under an ever-increasing virtual pile of email.</p><h3>Consider lowering your rate</h3><p>I usually don’t work by the hour. Instead, I take on whole projects, estimate them and give ballpark figures. My process is always in flux, however, to reflect that I’m always learning better ways to approach things. For example, I’m keenly interested in the <a href="http://neilkillick.com/2013/01/31/noestimates-part-1-doing-scrum-without-estimates/">No Estimates movement</a> and how it can positively impact my business. In a work drought, however, you must be flexible. Some money is better than no money, provided you are covering your costs. Don’t specifically start with a lower rate, but you may want to indicate that your rate is negotiable or that you are willing to offer a discount of your rate at this time. When working for friends and peers, consider discounting your rate simply because they are your friends. Doubly consider this if they are doing you a favour.</p><h3>Engage recruiters</h3><p>When business is good, I avoid using the services of recruitment agencies. They have their own overheads to cover and if you have built up a decent enough network and client base or if you advertise to a large enough group of people, they won’t be part of your business model. In addition, most roles that recruiters find candidates for are either permanent or long-term and are almost certainly monogamous (i.e. you must work for that role and only that role), which is usually not flexible enough for a consultant with more than one client.</p><p>When business is not so good, it’s worth checking with recruiters that you trust (choose wisely) to see if there are any companies that they know of that are looking for someone with your particular talents. If you have no choice but to do a short stint as a contracted-employee, then so be it. This all comes down to sacrifices you’re willing to make, as noted earlier.</p><h3>Look actively</h3><p>Opening your mouth to make announcements is only going to be as effective as the number of people who are actually listening at the time. It pays to get a little active in your search as well. I know you’ve already talked to peers, past clients and friends but this is only a little more active than that. Search industry mailing lists, newsgroups and newsletters. In my industry, as noted, Twitter is an excellent way to get in touch with the developer community, so I search there too. There are Twitter accounts <a href="https://twitter.com/XcodeJobs">dedicated to retweeting jobs</a>, so find and follow all of those if applicable for your industry. If you’ve started engaging recruiters, then looking on sites like <a href="http://www.seek.com.au/">Seek</a> will expose you to more of them, so you can check there. If you’re game you could check <a href="https://www.freelancer.com/">Freelancer</a> or other similar sites, but I try to avoid these as they tend to encourage a bidding war as to who can develop the worst product for the least possible price. It’s not a really professional vibe. It’s been a while since I’ve used them, so I might be completely wrong, but consider that if you are paying through the nose to live in Sydney, Australia, you won’t be able to afford to outbid someone who is living in Bangladesh.</p><h3>Schedule your time and keep your head up</h3><p>A work drought isn’t a holiday. The time between Monday morning and Friday afternoon is still work time. Unless you’re well-buffered and you <em>are</em> actually on holiday (what are you doing reading this then?). Keeping to a work schedule is very important, especially if your office is your home and vice-versa. Psychologically, if you fail to keep a work schedule in these times, your motivation can drop off and your self-doubt and <a href="http://en.wikipedia.org/wiki/Impostor_syndrome">impostor syndrome</a> can skyrocket (be wary of these things anyway, but that’s for another article). Get up at a decent hour every morning, shower, eat breakfast (or however you normally do) and dress in your work clothes. Dressing in your work clothes means you are ready at a moment’s notice to attend an opportunistic meeting or go out to get something to feed yourself with (as motivation becomes a problem, this also can become a problem). Keep to your regular schedule of starting work, breaking and finishing work for the day. See below for more on what to fill your time up with if you have any doubt. Don’t start big sprawling projects. Budget your time as you would normally. Give yourself a break when you would normally — at the end of the work day and on weekends.</p><h3>Invest some time</h3><p>It’s possible that seeking work in a drought could take up the time of a full-time job, but it’s probably not a good idea. Keep in mind that the world keeps turning (I needn’t remind those of you who are currently harvesting wolf pelts at your front step), and if you’re in a rapidly changing industry like mobile apps then it’s important that you stay up to date. Once you’ve done enough to seeking to satisfy the burning fires in your gut, you should take some time to keep your skills up to date. Read up on industry news. Stay current. Stay actively involved. Take advantage of the available time to hone your skills or learn new ones. If your work drought happens to coincide with a huge industry event (like say <a href="https://developer.apple.com/wwdc/">WWDC</a>), then take full advantage by doing something that no-one else can justify doing. Attend those webinars. Mainline those session videos. Ravage those new docs. Discuss them with your peers. Become an even more knowledgable expert. Once this drought is over, and believe me, it will pass — just like everything else does, you’ll come out with a valuable advantage.</p><h3>Be kind to yourself</h3><p>Above all, be kind to yourself and be kind to the people around you. There’s no point in taking your current frustration out on any of them or yourself. You’re a professional, after all. This is part of the game. Recognise it as such and relax. Make sure you get good sleep. Naps are ok too. Don’t kick yourself or talk yourself down. It’s all just part of the game. Check in with yourself regularly. Judge how you’re doing with things. Don’t be afraid to reach out to others for help. Professionalism is one thing, pride is another. We’re all living, breathing human beings here. If you didn’t plan ahead successfully for the completely unpredictable future and you’re not perfect then that’s ok. You’ll certainly be better at it the next time this comes around. Take notes. Meditate. Live. Don’t panic. Stay calm. There are always options. Learn this part of the game. The right attitude can turn this seemingly scary time into a valuable career and life-affirming experience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=baeee89a0f7f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>