I wouldn't personally want to do this because gig economy work seems inherently risky and low-paying and my current job is not those things, but I see a more fundamental problem with the very idea of gig economy for software engineering. Gig economy is ideal for short-term, one-off tasks that are well-defined and effectively commoditized. Give me a ride somewhere. Buy my groceries. Carry a bed upstairs for me.<p>Once you get into something as complex as install a new shower for me, let alone design and install a new shower for me, there is a lot of value in things like long-term client/contractor relationships, word of mouth referrals, and the jobs need to be individually scoped and price negotiated. It gets further and further away from making any sense to have it be app-mediated. You could, of course, have software that aids contractors in managing customer relationships and scoping work, but that's just plain old-fashioned CRM and ERP, not gig economy.<p>Where I could see this maybe working is for very small discrete tasks, like lend me your computer for a consensual botnet to stress test my infrastructure, help with reviewing this single documentation pull request to ensure it's readable to an average person who isn't on the team already, but I don't think customers are largely in a position right now to be able to individually purchase something like 4 hours of work. The overhead isn't worth it from enterprises with convoluted and expensive purchasing processes. But there is not a sufficient value add for small businesses on top of just "hire a single tech guy to do everything for you," but then it's not a "gig" any more. It's just normal contract work.