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
Conversation
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
The creative conception in OSS often happens solo, or in a small tight-knit group, prior to the apparent “main” lifetime of the project.
2
15
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
This is an exciting observation.
In fact, we invented a new kind of development through which we produce pictures and narratives about anything inside software systems. It turns out that this compresses communication dramatically, and leads to new organizational possibilities.
1
1
It’s called #MoldableDevelopment and through it we construct custom tools for every single software development problem. These tools offer compressed views that then compress communication. They need to be custom to capture the essence of the problem at hand.
1
1
Ah, thank you! sent this my way a few weeks ago, and I was intrigued. One thing I’m missing from these resources—and I’d love to hear more about—is the interpersonal. How does it solve the typical remote creative collab problems?
I can offer our team experience as a case study. A write up is available here:
1