Recession Proof Developer – A How To
How do you survive an economic recession as a software developer, let alone thrive in it? That’s what we’ll focus on in this tutorial. You’ll learn 3 key approaches to make the most of a recession and how to be ready when the wind picks up again.
Here’s what we’ll focus on:
- The 3 pillars of recession-proofness: skills, projects and your network
- Why building your skills, and the ability to learn, are important
- How to build a project, and why, and how that helps you grow
- What steps to take to build a opportunity-rich network
- That surviving and thriving in a recession requires a shift in mindset
This tutorial is especially suited for:
- People who want to make a career switch into app development or tech/software in general
- Entrepreneurs, freelancers and side-project developers who want to make the most of their business, job and side-projects
- People who are currently unemployed, seeking work, or who are underwhelmed by their current job and hope to start a career in software or tech
Ready? Let’s go.
- How To: Recessions 101
- Build Your Skills
- Build Your Projects & Reputation
- Build Your Network & Assets
- Mindset Shift: A for Adversity
- Further Reading
This article was originally published in March 2020. It’s been updated in May 2021, because it’s still quite relevant.
How To: Recessions 101
I became a freelance software developer in 2008, right in the middle of the 2008 financial crisis. I didn’t know it at the time, but I had picked the worst time to become an entrepreneur since The Great Depression.
Since the start of 2020, the coronavirus/COVID-19 pandemic has the world in its grasp. We’ve seen plenty of lockdowns, regional outbreaks, businesses going bankrupt, people losing their jobs – and a tremendous cost in human life.
Economists have warned about signs of an upcoming recession before, and they expect that this pandemic is the last straw. Right now, the economic effects are ambiguous: there is an economic decline, but it’s also dampened by relief efforts. At the same time, many people are hit directly, financially, on a personal level.
Looking back at the last 100 years, recessions and crises happen regularly. Although no one knows when they happen, we do know that they happen every decade or so.
- 1973 and 1979 oil crises (oil embargo and subsequent stock market crash)
- Black Monday, 1987 (stock market crash)
- Dot-com bubble, 2000 (speculative investment in tech companies)
- Great Recession, 2008 (financial crisis, subprime mortgages)
Every recession is different, but in general, we can assert that people lose their jobs, their homes, income is reduced, we spend less money, crises affect health and life expectancy, etcetera, when a recession or crisis happens.
We’ve also overcome every recession, and climbed back up. Not unscathed, but in the long run OK again. The question of dealing with a recession isn’t “How can I avoid it?”, but it’s about “How can I deal with it?” Lean in, and don’t count on luck alone.
You don’t need a PhD in economics to understand what happens in a recession. Let’s look at a metaphor:
- Recession: You want to sail, but there’s no wind. What do you do?
- You could sit ashore waiting until the wind picks up. Bad idea!
- A better idea is to build a (better) boat/sail, in case the wind picks up.
- It’s also smart to build something else temporarily, to bridge the gap, like painting or maintaining boats in a dock.
In the next few sections, we’ll focus on different “boats” you can build as a software developer, or as someone aspiring to get into tech, and how you can get there.
Let’s dive in.
Technically, a recession, crisis and market crash are distinctly different things. Throughout this tutorial, we’ll refer to a recession as a “general, extended decline in economic activity.”
Build Your Skills
Imagine you’re a bookkeeper, so you do financial accounting for a living, and the year’s 2000. The Dot-com bubble is well underway, and you see tech companies go bankrupt left and right. Again, the shit is about to hit the proverbial fan…
What do you do? You learn to code. Your friends will call you crazy. Only an idiot is going to learn coding when software developers are losing their jobs. You respond: “Only an idiot stays on a sinking ship.” (A moot point, really. Only idiots stay away from all ships when one of ’em sinks.)
A year or so later, you’ve learned how to code web applications. With your knowledge of accounting, combined with coding, you’ve made an online bookkeeping platform for small businesses. And business is booming!
What bet did you make, exactly? You observed that the underlying principles of the Internet wouldn’t change. The Dot-com bubble was caused by speculative investments, not because the Internet or coding was a bad idea. You saw how it could connect people, and transform the way we create software.
Sure, you had to cut back on expenses, invest time into learning how to code, and you were worried your bet wouldn’t pay off. You took a risk, that’s for sure. It might not have worked!
Which is why you hedged your bet, too. Hedging simply means to reduce the risk of a negative outcome, while taking a “position” that can benefit you. In this scenario, you took a risk by learning how to code, but you padded that risk with secondary benefits:
- You could always go back to accounting and bookkeeping
- You could always use your programming skill in different ways
- You could capitalize on the meta-skill of learning, and learn a 3rd skill
Do you see where this is going? In times of crises, you don’t invest differently – but your environment does change. It’s not about making the right choice, it’s about finding the right insights to make a choice.
Instead of holding onto your hat, you let it go, because you’re going to lose it anyway. No one is stupid enough to stay on a sinking ship, but not everyone is smart enough to realize that the ship you’re on is sinking (and know what to do about it).
The anatomy of building a skill in a time of crisis, is to invest time now so you can turn a profit later. You get ready to move your skill from an area of low economic yield, to an area of high economic yield.
In the Dot-com bubble crisis, software development was a low-yield skill. However, when the crisis faded, the economics of the Internet hadn’t changed, which means software development is a high-yield skill again.
And even if that failed, you would have proven to yourself that you’re able to invest in a time of adversity, a hedged bet, which is something you can do again, again, again, and again, until you find a skill that sticks.
What skill are you going to learn, next?
Build Your Projects & Reputation
Just having a skill isn’t enough — you need to use it. That’s where the next pillar of surviving a recession comes in: build your projects and reputation.
Building a product or project has 2 benefits:
- It’s hard to worry about a recession, while you’re building interesting things. When you wash the rice, wash the rice! Take your mind off things.
- A skill equals knowledge plus experience, so you gotta practice your skillset to actually gain experience (and keep that skill).
What are you going to build? First, let’s define some categories:
- Scratch your own itch
- Build something as a service (freelancer)
- Build something for a company (employee)
- Build something for other businesses (entrepreneur)
- Build something for the sake of building
Let’s start with that last category, because it’s the simplest. You can build something today – a tool, a script, an app – just for the sake of building. You inevitably gain experience that way. And it’s fun!
- Building something comes down to solving problems, and those problems cause you to gain experience.
- Experience is nothing more than remembering and applying how you solved the exact same problem last time.
- Fix enough problems, and you start to see patterns: the same solution applied to similar but different problems. This is experience!
You can do this regardless of a recession. In fact, you may need to, because you’ll face some downtime anyway. What are you going to do during downtime?
I’ve deliberately written “build something” here, because you really can build anything. When you’re about to start a project, don’t worry about monetizing or scaling or maintaining it. They are nice problems to have. You can solve them later. Focus on the task at hand right now: getting started.
A few ideas for things you can build:
- Build a better thing. I, for one, really hate the default Music app on iPhone. I’d be happy to build a new music app, just for the sake of building, and learning the APIs/SDKs. The same goes for copying App Store apps (not merely cloning/plagiarizing) and transforming them into something new.
- Build a fix thing. At home, we’ve got those Philips Hue internet-connected lights. A feature that they miss, is the ability to fade out over 5-30 minutes with the press of a button. Guess what? I’ve got a Raspberry Pi, the Hue SDK, and a few hours to kill. (Queue training montage!)
- Build a new thing. This is the hardest, because everything is a remix anyway. A great approach is the X-for-Y, i.e. build a music player for 90’s synthwave enthusiasts, or web-based accounting software for yoga studios, or a social network for crazy cat ladies (and gents).
If you look at the 5 categories of projects you can build, you’ll see that they really start at building for the sake of building. The other categories are just add-ons. Services, B2B and getting hired are really just different verticals of building things. This is why it’s hard to get into something just for the money. It helps to (learn to) love it!
Speaking of money – how do we get from Raspberry Pi/Philips Hue hacks back to gainful employment? That’s where your reputation from building projects comes in. If you’re building projects, I recommend you to create an online showcase for yourself, and to find clients and/or employers by doing great work.
You can’t control the economy, but you can control what you build, so you have some influence over the reputation you create for yourself. If you showcase to others that you’re a Reliable Builder of Things, they’re more likely to hire you.
You’ll need to apply, do interviews, get hired – this is a challenge in an economic recession, but less of a challenge had you done nothing at all. Meanwhile, you can pad your income a bit by doing individual sales of that app you launched in the App Store, or find some freelance clients.
Which leads us to our 3rd fundamental recession-proof approach: assets.
Build Your Network & Assets
An asset is a thing that generates a (potential) upside, that increases in value over time. The most basic asset is money. Money generates a financial upside, like interest or dividend, and if you invest your money into stocks, bonds, indices, funds (all are assets) your money gains more value over time.
A skill is an asset too, provided you can move it from a low- to high-yield environment. Are you selling water in the desert or snow on the North Pole? Your reputation is an asset as well, and so is the network of people you build while creating your projects.
If you showcase your work, and promote it, you’re likely to come across people who can amplify the benefits of your work – and that’s your network. If your app helps people, your network can help you help more people. It’s a virtuous cycle.
The cool thing about assets is that they appreciate over time. An asset has ups and downs, much like publicly traded shares in a company. You’ve got good days, when the share prices goes up, and bad days, when it goes down. In a recession, you’ve got a ton of bad days. But, stick ’em out, and the price goes up – provided they were good positions in the first place.
Building a network isn’t as volatile as the stock market, but their principles are the same. Say you’ve built a project (for free), and you promoted it, and someone saw it, and the recession is over, and they refer you to a company that’s looking for a new developer. That’s your skills, projects, reputation and network in action!
How do you build a network? You meet people, and you discuss your work. A few ideas:
- Go to tech meetups in your area. Talk to people, learn about different tools and technology, and show them your work. Ask for feedback and criticism, and have a good time.
- Attend a conference. You can present your own work, if you get the chance. You can hear about other’s ideas and projects. And you can connect with the other attendees. (Works well online if you’ve got live breakout rooms, or interactive live sessions.)
- Document and share your work. This includes starting a YouTube channel, vlogging on TikTok, interviewing people in your industry on a podcast, and contributing open source code on GitHub. If you don’t publish, it doesn’t count!
Don’t worry – the above ideas also work when your country is in lockdown because of a virus epidemic. The dynamics may change, but you can meet people online, organize online conferences, and share your work that way.
Mindset Shift: A for Adversity
Yes, this 3-step approach to survive and thrive in an economic recession is going to take effort. It’ll take more effort than you anticipated. Instead of driving to work, you’ve lost your job, sold your car, and you’re stuck at home watching how-to videos about programming. It sucks!
It’s going to get better, and it’s going to get worse. Economic recessions are like that, and that’s OK. Your only mistake was thinking stuff would stay OK forever. Next time, an economic downturn won’t mean a personal downturn for you, because you’ve learned something new today.
The cool thing is that the strategies that we’ve discussed today work well in good times, and in bad times. You’ll get better at assessing and creating opportunity, regardless of whether the market moves in your favor.
Adversity is a great teacher, because it helps us grow. When you stagnate, you don’t grow. Chaos, adversity, entropy, suffering, a decline into disorder – that’s here to show us one thing: get a move on.
Note: It’s like the dollar cost averaging stategy for investing in stocks and bonds, applied to learning skills. Instead of investing your energy into learning a skill once (i.e., a university degree), you invest 1/10th of the energy in increments over the same period (i.e., Udemy/Coursera/Khan Academy courses). This way you don’t put your eggs in one basket, and you’re distributing the risk over a greater period of time. You’re less likely to get duped right after you graduate, and you’re able to move with the market’s ups and downs.
Awesome! We’ve really gotten somewhere, haven’t we? In this tutorial, we’ve walked through the 3 pillars of making something of yourself when the shit has hit the fan. Here’s what we discussed:
- How recessions work, and why avoiding them doesn’t help
- How building your skills are the first step to surviving a recession
- That your projects build your reputation, and sharpen your skills
- How building a network helps you come out on top
Want to learn more? Check out these resources:
- How to Work Productively from Home
- 7 Reasons Why You Should Learn To Code
- Learn Swift Programming The Simple Way
- How To Get Freelance iOS Development Projects
- How To Build A Profitable App With A Pro Upgrade
- How To Take Your First App Project From Start To Finish
- How To Become A Professional iOS Developer
- How To Beat The iOS Coding Interview
- Next Gold Rush: Building iOS Apps For Enterprise And B2B
Code Swift right in your browser!
Go to the Swift Sandbox