Indeed, I encounter that same idea in some people. I'm unsure where it comes from, it feels like reading and extrapolating from something more reasonable (it's like the "one test per line" I sometimes hear about). Bad idea indeed, it's fine to have several assertions, it's probably often required to avoid complexity explosion in your tests. This of course doesn't mean your test should become unfocused.

Nice succinct form to present a strategy.

Interesting take on burnout as an organizational phenomenon and the consequences. This is not simply about the amount of work.

Interesting framework for sustaining a strategic train of thoughts for the long term. This can't be a fix thing, it needs to live and breather which this approach seems to foster.

Very important topic. Nice to see more such teams appearing and thinking now focusing on how to structure them.