Maybe it would help if you guys knew why the "dev time" defense is so stupid.
Even if you were right, which is extremely unlikely, the response is still "So?"
Guy suggests destructible environments. That's probably not gonna happen. We all know that. You say "tHaTS toO hArD TO CoDE!!1" The response is still, "So?"
Whether you're right or you're wrong, and you are probably wrong, the response is still "So?" The best possible outcome is zero contribution and there's a significant chance, approaching certainty, of a negative effect on the conversation.
It's objectively a stupid thing to say.
It'd be like someone telling you about a goal or a dream and you telling them, "That's too expensive." I understand that people don't realize the chilling effect this type of thing has, because people do exactly that. That's why I'm suggesting guidance and coaching.