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?
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.
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.
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.
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.
I have a different experience. We are able to create (and execute) quickly while being completely remotely and async.
Code is certainly not prose. Exhibiting the inside of systems through pictures changes the conversation significantly.
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.
Good question. May just be survivorship bias: you are aware of OSS which achieved product–market fit and growth via its conception—but most OSS dies silently, not useful enough to attract growth. Tech companies are noisier, can use $ to leverage creative collab during conception.