I wonder if the future (or maybe present) of software development is a lot like construction trades. Many work for bigger firms, but there are loads of drywallers, carpenters, roofers, electricians and plumbers - though the latter two are a bit different, that are essentially independent, and get called in either directly by a customer or by a contractor to deliver part of a project.
This model works well for trades and notably is absent any real management - sub-trades are hired to deliver on an outcome, not to be "managed " and they take responsibility for the quality of their work.
Construction tradespeople I know would not be interested in demand generation or fintech software or whatever else this article is pushing. I'd expect the same from shrewd solo operators, that are focused on doing their trade well and not on getting caught up in management activities. I say this because although these sound attractive to the management class, I think selling SaaS management tools to solo operators is a tougher nut to crack than people realize
Except for the General Contractor taking a % of all billing to manage the entire process? Construction is what gave us Gantt charts, and large projects are incredibly well-structured and managed so that heavy, expensive equipment and material isn't delivered when it can't be used.
If what's being 'built' is basically a copy/clone of something that a person or team has done before, sure.
Coordinating discovery and planning across disconnected "software tradespeople" isn't easy. In physical construction, it's usually pretty easy for contractor A to indicate that he is blocked by contractor B. "I can't drywall until the electrics are in". People wouldn't demand that the drywall be put in anyway just so they could hit some arbitrary "velocity" goal, for example. This is much harder to decipher and work around in software pieces, especially by disconnected vendors and contractors.
It is already like that for companies whose main business isn't selling software.
Consulting companies, or freelancers, get hired to work on tickets, or do small updates to existing software that is driving business processes, factories, .....
They usually don't have any IT in-house beside a couple of project managers that take care of all external contractors and what they are supposed to do.
It is also quite common in the games industry since it exists, hence why 3D APIs are less relevant as many in FOSS comunity think, there are contractors whose main business is porting titles and they still take less than having bigger teams in-house.
The interface between two pieces of construction work, done by two different kinds of contractors is, generally speaking, far less variable than the interface between two different pieces of software, or a piece of software and a piece of hardware, or a piece of software, and a business process.
It's not uncommon for software to discover that the interface point it's supposed to work with is the digital equivalent of a plumber laying down pipes made out of sugar, instead of PVC.
have you ever worked in contruction or even fixed stuff around your house?
:-) its crazy how non-fitting stuff is. for nearly every slightly different job you can better expect to buy new tools or find some other hack around.
the difference IMO is that people realize that once something is up, the cost of change is HUGE. In software, (non programmer) people somehow expect that this is not so and everything always can be rewritten differently.
> The reality of a lot of 'solo' programming work is just part-time pay, full-time responsibility, with no benefits or job security.
This might be true, but the reality is also that it is doable to actually reach a point where quitting your job to pursue your side-project is a viable option. I think the problem with a lot of software engineers/developers is that they lack the skills like marketing and selling in order to scale. Typically, and I've done this myself, we develop something that we think is cool, aaaaaaand... that's it. You stall. Educating yourself in different areas (if you're going 100% solo), you can use that knowledge to reach a point where you can see your product take shape and use it to sustain yourself.
In my career, solo programming gigs have generally been much better paid compared to employee jobs, with the right tax planning and living in the right countries.
Even ignoring tax advantages, contractor's daily rates tend to include things I rarely use like sick pay, holidays, missed stock options.
Unless you're working for a FANG where stock options are pretty much guaranteed money, working solo is generally a good deal.
If the value you're bringing to the table is that you live in a cheap country, you'll get paid less (but still a lot compared to your cost of living, most likely)
Why does the chart title include the words "vs. the great recession"? I'm having trouble ascertaining precisely what the y-axis is. There doesn't seem to be any data from the great recession on the chart, despite the title clearly implying that there should be.
The chart title comes from the actual paper (linked right above the graph: https://www.nber.org/system/files/working_papers/w28912/w289...) that includes two charts (COVID-19 and Great Recession), but the article only includes the first chart (so it makes less sense in the context).
There used to be pirates, there are still pirates. Various levels of institutionalization amongst humans. Doctors were traditionally solo practitioners, but there’s been a lot of consolidation there, particularly in cities. Software is pushing in the other direction, particularly with bitcoin. I mean you could even have a piracy stack as a meta layer on top of civilization. Kind of like the Mormons.
This model works well for trades and notably is absent any real management - sub-trades are hired to deliver on an outcome, not to be "managed " and they take responsibility for the quality of their work.
Construction tradespeople I know would not be interested in demand generation or fintech software or whatever else this article is pushing. I'd expect the same from shrewd solo operators, that are focused on doing their trade well and not on getting caught up in management activities. I say this because although these sound attractive to the management class, I think selling SaaS management tools to solo operators is a tougher nut to crack than people realize