The 4 Levels of Freedom For Software Developers
Join the DZone community and get the full member experience.Join For Free
for quite some time now i’ve been putting together, in my mind, what i think are the four distinct levels that software developers can go through in trying to gain their “freedom.”
for most of my software development career, when i worked for a company, as an employee, i had the dream of someday being free. i wanted to be able to work for myself. to me, that was the ultimate freedom.
but, being naive, as i was, i didn’t realize that there were actually different levels of “working for yourself.” i just assumed that if you were self-employed, you were self-employed. it turns out most software developers i have talked to about this topic have the same views i did—before i knew better.
i’ve written in the past about how to quit your job , but this post is a bit different. this post is not really about how to quit your job, but the different levels of self-employment you can attain, after you do so.
the four levels
the four levels i am about to describe are based on the level of freedom you experience in your work; they have nothing to do with skill level. but, generally we progress up these levels as we seek to, and hopefully succeed, in gaining more freedom. so, most software developers start at level one, and the first time they become self-employed, it is usually at level three—although it is possible to skip straight to three.
here is a quick definition of the levels (i’ll cover them each in detail next.)
- employed – you work for someone else
- freelancer – you are your boss, but you work for many someone elses
- product creator – you are your own boss, but your customers determine what you work on
- financially free – you work on what you want when you want; you don’t need to make money
i started my career at level one and bounced back and forth between level two and level one for quite awhile before i finally broke through to level three. i’m currently working on reaching level four—although, i’ve found that it is easy to stay at level three even though you could move to four.
along the way, i’ve found that at each level i was at, i assumed i would feel completely free when i reached the level above. but, each time i turned out to be wrong. while each level afforded me more general freedom, each level also seemed to not be what i imagined it would be.
level one: employed
like i said, most software developers start out at this level. to be honest, most software developers stay at this level—and don’t get me wrong, there is nothing wrong with staying there—so long as you are happy.
at this level, you don’t have much freedom at all, because you basically have to work on what you are told to work on, you have to work when you are told and you are typically tied to a physical location. (throughout this post, you’ll see references to these three degrees of freedom.)
working for someone else isn’t all that bad. you can have a really good job that pays really well, but in most cases you are trading some amount of security for a certain amount of bondage. you are getting a stable paycheck on a regular interval, but at the cost of a large portion of your freedom.
now, that doesn’t mean that you can’t have various levels of traditional employment. i think there are mini-levels of freedom that exist even when you are employed by someone else. for example, you are likely to be afforded more freedom about when you start and leave work as you move up and become more senior at a job. you are also likely to be given a bit more autonomy over what you do—although agile methodologies may have moved us back in that regard.
you might even find freedom from location if you are able to find a job that allows you to telecommute. in my quest for more freedom, i actually made a trade of a considerable amount of pay in order to accept a job where i would have the freedom of working from home. i erroneously imagined that working from home would be the ultimate freedom and that i would be content working for someone else the rest of my career, so long as i could do it from home. (don’t get me wrong, working from home has its perks, but it also has its disadvantages as well. when i worked from home, i felt more obligated to get more work done to prove that i wasn’t just goofing off. i also felt that my work was never done.)
now, like i said before, more people will stay at level one and perhaps move around, gaining more freedom through things like autonomy and a flexible working schedule, but there are definite caps on freedom at this level. no one is going to pay you to do what you want and tell you that you can disappear whenever you want to. you are also going to have your income capped. you can only make so much money working for someone else and that amount is mostly fixed ahead of time.
level two: freelancer
so, this is the only other level that i had really imagined existed for a software developer, for most of my career. i remember thinking about how wonderful it would be to work on my own projects with my own clients. i imagined that as a freelancer i could bid on government contracts and spend a couple of years doing a contract before moving on to the next. i also imagined an alternative where i worked for many different clients, working on different jobs at different times—all from the comfort of my pjs.
when most software developers talk about quitting their jobs and becoming self-employed, i think this is what they imagine. they think, i like i did, that this is the ultimate level of freedom.
it didn’t take me very long as a freelancer to realize that there really wasn’t much more freedom, working as a freelancer, than there was working for someone else. first of all, if you have just one big client, like most starting freelancers do, you are basically in a similar situation as what you are when you are employed—the big difference is that now you can’t bill for those hours you were goofing off. you will likely have more freedom about your working hours and days, but you’ll be confined to the project your client has hired you to work on and you might even have to come into their office to do the work.
this doesn’t mean that you don’t have more freedom though, it is just a different kind. if you have multiple clients, you have more control over your life and what you work on. you can set your own rate, you can set your own hours and you can potentially turn down work that you don’t want to do—although, in reality, you probably won’t be turning down anything—especially if you are just starting out.
don’t get me wrong, it is nice to have your own company and to be able to bill your clients, instead of being compelled to work for one boss who has ultimate control over your life, but freelancing is a lot of work and on a daily basis it may be difficult to actually feel more free than you would working for someone else.
given the choice of just doing freelancing work or working for someone else, i’d rather just take the steady paycheck. i wouldn’t have said this five years ago, but i know now that freelancing is difficult and stressful. i really wouldn’t go down this road unless you know this is what you want to do or you are using it as a stepping stone to get to somewhere else.
from a pay perspective, a freelancer can make a lot more money than most employees. i currently do freelance work and i don’t accept any work for less than $300 an hour. now, i didn’t start at that rate—when i first started out $100 an hour was an incredible rate—but, i eventually worked my way up to it. (if you want to find out how, check out my how to market yourself as a software developer package.) the big thing though, is that your pay is not capped. the more you charge and the more hours you work, the more you make. you are only limited by the limits of those two things combined.
level three: product creator
this level is where things get interesting. when i was mostly doing freelancing, i realized that my key mistake was not in working for someone else, but in trading dollars for hours. i realized that as a freelancer my life was not as beautiful as i had imagined it. i was not really free, because if i wasn’t working i wasn’t getting paid.
i actually ended up going back to fulltime employment in order to rethink my strategy. the more and more i thought about it, the more i realized that in order to really gain the kind of freedom i wanted, i would need to create some kind of product that i could sell or some kind of service that would generate me income all the time without me having to work all the time.
there are many ways to reach this level, but perhaps the most common is to build some kind of software or software as a service (sass) that generates income for you. you can then make money from selling that product and you get to work on that product when and how you see fit.
you can also reach this level by selling digital products of some sort. i was able to reach this level through a combination of this blog, mobile apps i built, creating royalty generating courses for pluralsight and my own how to market yourself as a software developer package. (yes, i have plugged it twice now, but hey this is my blog—and this is how i make money.)
you have quite a bit of freedom at this level. you no longer have any real boss. there is no pointy-haired boss telling you what to work on and you don’t have clients telling you what projects to work on either. you most likely can work from anywhere you want and whenever you want. you can even disappear for months at a time—so long as you figure out a way to handle support.
now, that doesn’t mean that everything is peaches and roses at this level either. for one thing, i imagined that if i was creating products, that i would get to work on exactly what i wanted to work on. this is far from the truth. i have a large degree of control over what i choose to work on and create, but because i am bound by the need to make money, i have to give a large portion of that control over to the market. i have to build what my customers will pay for.
this might not seem like a big deal, but it is. i’ve always had the dream of writing code and working on my own projects. i dreamed that being a product creator and making money from my own products would give me that freedom. to some degree it does, but i also have to pay careful attention to what my audience and customers want and i have to put my primary focus on building those things.
this level is also quite stressful, because everything depends on you. you have to be successful to get paid. when you are an employee, all you have to do is show up. when you are a freelancer, you just have to get clients and do the work—you get paid for the work you put in, not the results. when you are a product creator, you might spend three months working on something and not make a dime. no one cares how much work you did, only results count.
as far as income potential, there is no cap here. you might struggle to just make enough to live, but if you are successful, there is no limit to how much you could earn, since you are not bound by time. at this level you are no longer trading hours for dollars.
to me, it isn’t worth striving for level two, it is better to just work for someone else until you can reach level three, because this level of freedom is one that actually makes a big difference in your life. you still may not be able to work on just what you want to work on, but at least at this point—once you are successful—all the other areas of your life start to become much more free.
level four: financially free
i couldn’t come up with a good name for this level, but this is the level where you no longer have to worry about making money. one thing i noticed when i finally reached level three was that a large portion of what was holding me back from potentially doing exactly what i wanted to do was the need to generate income.
now, it’s true that you can work on what you want to work on and make money doing it, but often the need to generate income tends to influence what you work on and how you work on it. for example, i’d really like to create a video game. i’ve always dreamed of doing a large game development project. but, i know it isn’t likely to be profitable. as long as i am worrying about income, my freedom is going to be limited to some degree. if i don’t have passive income coming in that is more than enough to sustain me, i can’t just quit doing the projects that do make me money and start writing code for a video game—well, i could, but it wouldn’t be smart, and i’d feel pretty guilty about it.
so, in my opinion, the highest form of freedom a software developer can achieve is when they are financially free. what do i mean by financially free though? it basically means that you don’t have to worry about cash. perhaps you sold your startup for several millions of dollars or you have passive income coming in from real estate or other investments that more than provides for your daily living needs. (for some good information on how to do this or how this might work, i recommend starting with the book “rich dad poor dad” .)
at this level of freedom, you can basically do what you want. you can create software that interests you, because it interests you—you aren’t worried about profitability. want to create an android app, just because, go ahead. want to learn a new programming language, because you think it would be fun—go for it.
this has always been the level of freedom i have secretly wanted. i never wanted to sit back and not do anything, but i’ve always wanted to work on what interested me and only what interested me. every other level that i thought would have this freedom, i realized didn’t. i realized that there was always something else that was controlling what i worked on, be it my boss, my clients or my customers.
now, this doesn’t mean that you can’t still make money from your projects. in fact, paradoxically, i believe, if you can get to this stage, you have the potential to make the most money. once you start working on what you want to work on, you are more likely to put much more passionate work into it and it is very likely that it will be of high value. this is where programming becomes more like art. i don’t have any proof of this, of course, but i suspect that when you don’t care about making money, because you are just doing what you love, that is when you make the most of it.
don’t get me wrong, you might be able to focus on doing what you love, even if you aren’t making any money. i know plenty of starving artists do—or at least they tell themselves they do—but, i can’t do it. i’ve tried it, but i always feel guilty and stressed about the fact that what i am working on isn’t profitable. in my opinion, you really have to be financially free to experience true creative freedom.
i’m actually working on getting to this level. technically, i could say i am there now, but i am still influenced greatly by profitability. although, now, i am not choosing my projects solely on the criteria of what will make the most amount of money. i am turning down more and more projects and opportunities that don’t align with what i want to do as i am trying to transition to working on only what interests me as my passive income is increasing.
what can you gather from all this?
well, the biggest thing is that freedom has different levels and that, perhaps, you don’t want to be a freelancer, after all. i think many software developers assume working for themselves by freelancing will give them the ultimate freedom. they don’t realize that they’ll only be able to work on exactly what they want to work on when they are actually financially free.
so, my advice to you is that if you want to have full creative control over your life and what you work on, work on becoming financially free. if you want a high degree of autonomy in most of the areas of your life, you should try to develop and sell products. if you are happy just being your own boss, even if you have to essentially take orders from clients, freelancing might be the road for you. and, if all of this just seems like too high of a price to pay, you might want to just stay where you are at and keep collecting your weekly paychecks—nothing wrong with that.
Published at DZone with permission of John Sonmez. See the original article here.
Opinions expressed by DZone contributors are their own.
Security Challenges for Microservice Applications in Multi-Cloud Environments
Micro Frontends on Monorepo With Remote State Management
Integration Testing Tutorial: A Comprehensive Guide With Examples And Best Practices
What to Pay Attention to as Automation Upends the Developer Experience