[coding123]

I think it's dangerous when we look at gigification as a "who cares it will work out somehow".

Imagine how up-in-arms if they gigified programming. It has already happened in places, but what if they wholesale a price per line of code?

This will get a lot of replies but honestly, a codebase that is spaghetti from gigification may be cheaper than non-spaghetti codebase at 100k - 200k/year * number of developers and work just as well for the domain it is in.

If you can put the "it won't work" aside - imagine they figure out that it does. That rage right now - how is that not applicable to the people getting gigified right now?

[Jensson]

> Imagine how up-in-arms if they gigified programming

Programmers would be up in arms in love with gig work and demand it everywhere if it turned out to actually work. The main problem with WFH is that you still have to work a set hours per week, gig work is the ideal. If you want to work 80 hours one week and 0 hours the next week you can do so. Gig work also means no deadlines, no manager, no long term worries, just write code and get instant money and feedback. The only reason you don't see developers clamoring for gig work right now is that they don't think gig work is possible for development.

[tick_tock_tick]

People complain about "gigifiation" because of things that has been traditionally tied to employment (health insurance, 401k, etc) not the gig part of it. If someone figured out how to do it I'd assume most programmers would be all over it.