Maybe you're right. Obviously, if this advice helps people, then I should just back off. It's true that removing code is better than adding it, and that code i

Maybe you're right. Obviously, if this advice helps people, then I should just back off. It's true that removing code is better than adding it, and that code is a liability. And I admit that I needed to hear that early in my career. But the article acknowledges that "over-adherence to [that] dogma can be counter productive". Great--so how can I tell if I've gone too far? How do I know if I should write more code or less code? How do I know if my code is "dumb" enough? The article does not help with that. Saying that "code is a liability" is not actionable advice. Edit: In contrast, I found this article full of actionable advice: https://tidyfirst.substack.com/p/mastering-programming https://tidyfirst.substack.com/p/mastering-programming