Yeah, and it's horrible advice. If you're an EM or higher, you still wind up making decisions with heavy technical impact, even if it's "this pitch from a Senior Engineer on my team is smart, let's do it."

You don't have to be the best programmer, but you need to be able to have thoughtful technical conversations with the in-the-weeds engineers, and represent their work to the wider org. If your mental model diverges with the day-to-day reality, your judgment breaks down along with it, and you're going to wind up being the problem instead of being an asset to your teams.