|
|
|
|
|
by cgrealy
2178 days ago
|
|
The point of Lego is not the zero glue, the point is that all components share a common interface. >>What often happens with software development is that despite all the abstractions that get built while building one piece of software, it often turns out those abstractions can't be just pulled out and reused in another context because often those abstractions are too leaky. My question is whether a non-leaky abstraction is even valuable. Look at a real world example of non-trivial component reuse: a vehicle engine. It has a single purpose: convert chemical energy to kinetic energy, and they're really expensive to develop. But you can't just drop a v6 into a Tesla. |
|
E.g. it's a clear boundary between teams that collaborate on the "car" system, it's something some engineers specialize in that is quite different from "suspension system" (and such knowledge can be carried across engine design instances).
But you're right, when we're talking about LEGO-style composability, as you said, it's about having pieces that fit together and can be rearranged in many ways, and the real world is far messier and rarely you have universal composability; there are instances of "bounded" composability; e.g. the tyres for my car likely fit many other similar vehicles, but not all.