I think I understand the point the author is trying to make, but I think they end up accidentally making too strong of a claim. Sometimes there is /essential c

I think I understand the point the author is trying to make, but I think they end up accidentally making too strong of a claim. Sometimes there is /essential complexity/, but it is far from always. I think the line of thinking espoused by the author leads to less simplification and encourages a "well, the complexity has to live somewhere, so why bother?" type of approach. However, reducing complexity is often possible, and it usually comes before the implementation stage. Reducing complexity sometimes means solving a different problem.