I hadn't heard that before, it's great.

I like how he states that simpler software doesn't necessarily mean fewer components (roughly quoting). Where the article argues for fewer boxes and arrows. It's hard to argue specifics, because the article isn't getting into them, but sometimes more boxes and arrows makes things simpler. If you don't have multiple boxes, what do you have? One box of spaghetti?

I also disagree with the article that engineers like complexity. I've maybe known a couple, but usually they are really junior, or really unpopular.