There’s a similar guideline in the software world:
There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.
There’s a phrase that the tech world uses to describe the kind of people you want to hire: “smart, and gets things done.” I’m willing to grant “smart”, but what about the other one?
The sequences and HPMoR are fantastic introductory/outreach writing, but they’re all a few years old at this point. The rhetoric about SI being more awesome than ever doesn’t square with the trend I observe* in your actual productivity. To be blunt, why are you happy that you’re doing less with more?
*I’m sure I don’t know everything SI has actually done in the last year, but that’s a problem too.