That led to the idea that open source projects need to be housed in large foundations 21/
-
-
In fact, it's important that we are allowed to do so in order to avoid our entire life becoming a series of meta-debates 32/
-
But we should treat them as shortcuts and nothing more 33/
-
And we should revisit our third, fourth and fifth order ideologies very regularly 34/
-
There's a good chance that some part of the chain of reasoning will change sooner than you think 35/
-
The diff between the drag on progress caused by opaque ideologies and the acceleration caused by transparent ones is orders of magnitude 36/
-
Just like compound interest, the different magnifies and accelerates. 37/
-
Finally, while tradeoff calculations can change in a blink, human infrastructure cannot 38/
-
One of the benefits of ideological shortcuts is that you can build more infra around them that lets a society or tribe work productively 39/
-
But these abstractions, which work beautifully for the fixed point, degrade over time and eventually fail competitively 40/
-
We need to use these shortcuts to build abstractions, but groups built around them need to revisit them regularly 41/
-
And then, they must help each other migrate in a way that doesn't cause upheaval and that preserves as much shared value as possible 42/
-
Change is inevitable, and that makes the process of adapting to in inevitable as well 43/
-
One approach is to resist ideological shortcuts and examine every problem by doing the full cost calculus 44/
-
But this is incredibly expensive and isn't competitive with newer groups that operate on relatively recent ideologies 45/
-
Because they get the benefit of the shortcuts and you don't 46/
-
Instead, we have to 1. create shortcuts but remember their chain of reasoning 46/
-
2. Try to predict how likely a given assumption is to change, and don't build too many shortcuts on top of it 47/
-
3. Build communities on top of the more stable assumptions 48/
-
4. Revisit the primitive assumptions regularly, and when they change, revisit the derived shortcuts 49/
-
5. Have a process for migrating your community towards the new, relatively stable assumptions, before competitiveness suffers too much 50/
-
People often forget that this process has no end, and accept opaque ideologies that match the current fixed point in time 51/
-
But the process is destined to repeat, again and again and again. 52/
-
Productivity and competitiveness come from embracing this reality and building it into the core of communities. 53/
-
Of course, these shortcuts are contextual and domain specific as well 54/
-
Operating systems encapsulate the most general of these shortcuts. 55/
-
Programming languages get more specific (scripting lang vs. systems lang) 56/
-
And frameworks get even more domain specific 57/
-
That gives us a way to share the most general & stable shortcuts, breaking up into smaller groups for experimental/domain specific ones 58/
-
But ultimately, communities oriented around operating systems, languages and frameworks have a fighting chance ... 59/
-
at organizing around these changes. 60/
- 11 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.