Conversation

Open source projects tend to be remote-first simply because there is no budget for an office. Why does this seem to work for open source to a greater extent than for tech companies?
44
38
290
My sense is that the creative conception phase of a project (and subsequent definitional shaping) is most weakened by remote collab. Most open source work is about execution, maintenance, incremental improvement—which can more easily happen remotely.
1
1
39
Is that true, or is it that open source projects tend to be CLI-driven...and so what you're creatively collaborating on is text vs images, and so that's easier to work on remotely? If can identify the active ingredient here, that might help with "remoting" existing cos.
4
3
I’m sure there are exceptions, but it’s hard for me to think of examples of OSS where significant creative conception is being done with many people remotely. Even in crypto, the conceptual work is often driven by solo individuals and coworking meetups.
1
4
Your question about text vs images is a good one. My instinct is that it’s more about creative-vs-execution than medium: highly creative co-authoring of prose *also* sucks to do remotely.
2
1
6
Why is there more creative work for a tech company than an open source project, though? A big project like Django or Ethereum is as complex as a tech company. Maybe it's because the customers are the creators, so there is less market research, no sales process, etc? Hm.
1
1
7
To your point - So many open source projects today are spun out of traditional tech companies - presumably where they were conceptualized and formed by in-office teams working closely together.
1
1
2
Show replies
Replying to and
I think it's also safe to say that most OSS projects suffer from a lack of UX/design-driven investment on the part of the creators.. most of this "UX" comes from indirect abstractions built on top of the OSS, but indirectly. See every SaaS app: sexy UIs atop OSS tapestries.
1
4