"Structural Advantages for Software Developers to Leverage and Destroy"
> Free and open source software represents a post-scarcity methodology, but it does not fill our bellies or pay for our roofs; we do that for ourselves. Given the nature of our works, tech workers are in a unique position to call into question scarcity itself: if we can pay for our labor without paywalls, we can build post-scarcity systems.
@garbados it doesn't suck. In fact it's very good.
However throughout the read I couldn't shake the feeling that there aren't enough people who care and in the ranks of software developers I feel the numbers are even smaller.
My feeling is that this craft is overrun by a toxic mix of the startup culture and the kludge-it-up-in-a-weekend culture.
In stark contrast with the doctors and architects I have met, who mostly respect their profession way more, and grasp the impact of their choices.
@qwazix thanks :) i really appreciate the feedback
i think the numbers we need for a critical mass are much smaller than imagined, that we can make a big difference as small teams dedicated to maintaining portions of our shared infrastructure, that these efforts can operate in parallel to pushes for unionization. we don’t have to wait for bosses to consent or for scabs to repent to take control of the things we have already built.
@garbados yes! Love it. I'm in. How do we start? I think tech coops/collectives are definitely part of the answer
@garbados reading now. Also pertinent is this piece by rich bartlett http://richdecibels.com/stories/courage-before-hope/courage-before-hope.html
@garbados I found this really interesting, and it expresses very well the reasons my worries in working in software. Unfortunately I think I didn't quite understand the analogy to guilds and will have to reread it when I'm more awake...
A Mastodon instance for cats, the people who love them, and kindness in general. We strive to be a radically inclusive safe space. By creating an account, you agree to follow our CoC.