[userbinator]

OSGi is essentially classic bureaucractic enterprise-ism meets OOP dogma cult, and like all "hyperabstraction" in general, greatly decreases systems-level understanding and macro-simplicity (critically important for things like debugging) in order to favour micro-simplicity. To sum it up, "splitting a system into easier to understand parts until each part is trivially understandable causes the actual complexity to become hidden between the interaction of the parts."

[twic]

To sum it up, "splitting a system into easier to understand parts until each part is trivially understandable causes the actual complexity to become hidden between the interaction of the parts."

Is that in quotes because it's a quote? If so, from where? Or is this a form of emphasis?

[userbinator]

I'm not sure. Me and my coworkers have been saying similar things for a while, and it's not really that deep of an observation. Abstraction can't always magically make things easier. It just moves the complexity around, and often increases it if used unnecessarily.

[twic]

Right, it's very similar to things i've said too, but clearly and succinctly put!

I see a similar problem with the common preference for unit tests over integration tests. The mistakes in a system tend to be in the interactions between parts, not in the parts themselves, and by construction, unit tests can't test those.

[gfodor]

If this were printed on a wall somewhere at my first job it probably would have accelerated my career by a decade or so.

[taeric]

As the sibling posts say, that is a great quote and insight. I'm curious if you have more exploring the idea?