I quite like software as a job but I think I'm going to end up working for myself, one way or another. I can work on a team but I prefer working alone; I also like having control over the direction of a project and being able to iterate as fast as I need to. This has led me to software consulting/contracting or just creating a "software studio." I'd love if someone who has done something similar to share their thoughts on this. Thanks!
If you need to get paid you aren’t “working for yourself” or controlling the project. Whomever pays for your work decides most of the parameters. That’s called freelancing or consulting.<p>You don’t “become” a freelancer or independent developer. That’s not an identity. You find customers who will pay you to deliver solutions to business problems. If you have a good reputation and track record and relationships with your customers they may trust you to make decisions about the project direction, tools and languages, schedule, etc.<p>Building a freelance practice takes considerable time and effort. I have some articles about that based on my experience (over 15 years freelancing) on my site typicalprogrammer.com.
I was in the same boat. Tried starting my own agency. Had a bit of success, but I was spending a huge chunk of my time just chasing money down. Then I stumbled upon a way to have my cake and eat it too: Becoming a Solutions/Sales Engineer.<p>It's all the upsides of running your own consultancy, without the downsides of chasing money and customers. I have generally flexible hours, tonnes of autonomy, and have a nice balance of getting to talk to people and coding. None of the coding I do is rocket science-level hard for me because I'm working with the same set of APIs every day, but is incredibly helpful for customers. My boss hardly ever tells me what to do, every week we have a 1/1, asks if the customers I'm helping are happy, and I tell him what I'm helping them do the following week.<p>It really is the best gig on the planet. I wish I would have known about this path sooner.
I am in the same boat. I have 12+ years of experience. I tired to launch a startup and it failed miserably.<p>I am considering Amazon IQ. If you are into AWS and can get the professional level certificates, you can use Amazon IQ platform to freelance. I have used Amazon IQ to hire before and I had good results. Your really need multiple pro level certificates to compete though.<p>I have tried Upwork, but it's been a not so good experience. I have my work history on the platform, but it doesn't seem to matter. I've worked at some top tier companies (one of the trillion dollar market cap SF big tech companies). I think Upwork requires building a portfolio tailored to the type of projects you would like to work on.
I can tell you what worked well for me - find a few other like minded devs/designers and one VERY GOOD biz dev person and you can have a lot of success as a co-op studio. We did this and we were immediately quite profitable from day one. Our model was pretty simple:<p>* Every full-time person (over 30 hours) is an owner in the company that is awarded an equal amount of company shares EVERY QUARTER.<p>* 10% of your earnings go to the company (of which you are now part owner)<p>* 10% of your earnings to the biz dev rainmaker that set up your contract<p>* Everything is decided democratically<p>This worked extremely well for us, but if you're at a small size (<6 owners) then you will have a heightened risk of single-point-of-failure because you can probably only afford to pay a single full-time biz dev person.
It’s <i>extremely</i> hard to engineer a product, sell a product, support a product, and administer a business all on your own. It really only works if you can escape a few of those hats through luck, unusual cleverness, or the right partner.<p>The easier road to having a lot of agency in your work is through consulting/contracting as you’ve already started. The more expertise your develop and the more reputation you earn, the more confidence you can bring to your recommendations and the more freedom your clients will give you. Once it starts churning, you make plenty of money and have lots agency and rarely need to look hard for work.<p>But that takes time. The most valuable advice, besides patience, is to be discerning about what clients you accept and retain. It can be tempting to take any client during a dry spell or to become enamored by a client with cool ideas, but some prospective clients will devour your soul and others will have financial trouble that leaves you with large unpaid invoices and little recourse. You can learn to spot this ahead of time and you want to develop that skill. Too extreme a bad client, or too many bad clients, will burn you out worse than any bad manager at bigcorp. So stay watchful and don’t be afraid to fire bad clients once you see things looking dicey.<p>Good luck!
It's not exactly what you have in mind, but my friend walked into local small businesses saying "Hey, can I make you a website?". Then he googled "how to make a website" and figured out how to drag and drop with WordPress. Literally no tech experience, just a few business cards, and it went uphill from there.<p>He gradually moved into SEO and marketing as his customers wanted that. Right now he has about 40 customers that give him consistent work.<p>To this day, he's still amazed that I can code and write CSS.
keeping your work pipe full take quite a bit of time. alot of jobs dont pan out, and when you think you've got steady work, it can suddenly disappear. also be prepared to deal with clients who really dont understand what they need and are just desperately hoping for someone to make their problems go away, but without empowering them. if they had control of their development, they wouldn't be hiring contractor. you've gotta try to make it work as best you can. because if you can, people will remember, and thats gonna help keep your pipe full later on.<p>unless you have a very niche skill that they really wouldn't normally hire a full time for. thats really the best ticket here, because those people are alot more respectful of your time, pay better, and are very clear about what they from you.<p>dont even try to get work on those job boards. i dont have any good suggestions on where to start getting jobs if you dont already have a network.<p>if you can keep all that going, its entirely possible to work part time, make good money, and have great control over your schedule and life choices. if you cant, then coming out of contractor into salary can be harder than transitioning between salaried jobs.
Right on, am sort of in a similar boat. Have been software contracting for a few years but it's still not truly "independent" dev work.<p>Probably the best way is to just do more independent software development. Personally think dog-fooding business tools are good to work on - solving your own problems.<p>One tough part about working independently is not being exposed to others' ideas. Keeping up on industry trends and continuing to learn via whatever means may also be relevant.
I have done this for 30 years now, but with a twist; I get clients for consulting, learn their business and then build software to help them and sell it to them and their competitors. My first products from 30 years ago (in pascal/Delphi) still sell. I am currently consulting for 5 clients and building a new product; keeps me up to date and the work interesting.
I have had similar thoughts lately, I currently work in govt in a job that isvery secure but isn't everything it could be. The thing that puts me off it is the unknowns around generative AI over the next few years - the cost of creating software is plummeting and the barriers to entry are dropping, language translation tools are going to enable a lot of high quality international developers (read: India) to better compete for remote work. Of course the flip side is a big increase in demand when there are lower costs, maybe it's the best time to do it.
build something and launch it. charge money for it. publish about it. repeat.<p>check out @indiehackers and @levelsio, and the book "start small stay small" by rob walling
> This has led me to software consulting/contracting<p>For better understanding your context, have you started being a consultant/contractor already?
I wrote an essay that kinda sorts describes my path into becoming a software consultant!<p><a href="https://nishantjha.org/essays/squeeze" rel="nofollow noreferrer">https://nishantjha.org/essays/squeeze</a><p>It’s early days for my writing and so I’d love feedback
I've been consulting for a decade. I never had a network starting out and just started contacting companies I found on job sites/indeed/craigslist.
"I can work on a team but I prefer working alone [...]" This to me is a red flag. Unless you're already pretty experienced, and have a large client base (or a small number of clients who keep you busy), it's nearly impossible to take on exclusively projects where you're the only developer. If you have the luxury of turning away clients with jobs that involve working with other developers, great. But most likely you're not in that position, and would be doing your clients a disservice by trying to do something alone that would be better served by working with other developers.<p>tl;dr Don't try to be a lone wolf. In the long run it hurts you, not to mention your clients. Learn to work with others.
I am having some difficulty in parsing out the situation you are trying to achieve.<p>If you're thinking "software studio" like "art studio" or "PR firm" or maybe a "legal practice" ? That sort of thing doesn't really exist yet (it may but it probably won't for another decade at least) but not to rain on your dreams let me share a bit how I reason to that;<p>Given the current working environment, there a few kinds of software "situations"[1] and each have their plusses and minuses.<p>The simplest is "employee" (which I know you're trying to get out of) but there is a reason that companies maintain a stable of employees whose only job it is is to create software. It is an economical way to spread the cost over a variety of software needs, especially for vertically integrated companies.<p>The next simplest is the software contractor. The client tells you what they need, maybe puts some parameters around it and gives you an unreasonable deadline[2]. The upside is you can pop these off and generally they will pay the rent. If you're specialized in a particular thing they can even pay more than the rent. The freedom to come and go as you please it a plus, that you need to line up the next one before the current one ends, kind of a pain. Evaluations are also often more stringent as the clients are typically paying you more per hour than they pay regular employees so they darn well get their money's worth.<p>A more complex one is developing a boutique software product and focusing on that. I have a good friend that developed all the software for some industrial control systems and they can just sell it again and again to people who are setting up factories or other control processes. I think the typical way these form is someone is contracting and starts reselling the software they wrote on one job to others. (note you need to include language in your engagement contract to do this!) But there are a lot of industries where they need an "out of the box" solution. One person I know did this for their local church and then resold the same package to half a dozen of the churches in town.<p>The important thing to understand is that software is <i>worthless</i>. I can be fun to write (I enjoy it tremendously and write software for fun) but to be <i>economical</i> it has to serve a purpose for someone who is generating some sort of economic product. And writing any software <i>product</i> has parts of the software that is boring/lame to write and that part of a project will always feel like a job.<p>There is however one way to write software for fun without having to deal with deadlines and impatient bosses, and that is to get a job teaching programming somewhere. You can write things and go over it with your students, you can see how they write things and help them get better at it. You do have to deal with "school politics" which is a thing but the software you right doesn't have to "do" anything, just be illustrative.<p>So if you had hired me as a coach and posed this question, the first thing we'd do is put yourself in your "software studio" and write down what your day to day looks like, who your customers are, and why they are paying you as opposed to hiring some contractor or a full time employee (FTE) to produce the software they need. Then work backwards from there to the present to get a handle on what milestones you might expect between your current situation and that one.<p>[1] I'm going to leave off the one where you work as an employee of a company that is growing and gives you stock options so that after some number of years you can pay yourself from gains on your investment portfolio and spend time writing what ever code you want. Perhaps surprisingly a lot of people fail at this (they have the means but just making up things to do is not one of the skills)<p>[2] I'm not sure why but of all the software contracts I've taken on over they years I have yet to have someone say, "Take as long as you need to get it <i>right</i>, that is so much better than getting it fast." :-)