> It takes good engineering to solve a problem, but it takes great engineering to solve a problem without creating three others elsewhere. Yeah that’s basicall

> It takes good engineering to solve a problem, but it takes great engineering to solve a problem without creating three others elsewhere. Yeah that’s basically what I mean. There’s essential complexity and incidental complexity. The first is the complexity that comes from the real world. The second is self imposed due to design choices or path dependency effects. Minimizing the latter is good engineering. I do maintain that every once I a while someone finds a way to radically cut complexity without losing essential capability. That’s genius, and it’s rare.