3 ms·
I dunno. Maybe. How about the practice of removing a test that fails? Literally, test fails, remove it, problem solved. Ship it. Sure there are build warnings,
by rendall 5y ago
I dunno. Maybe. How about the practice of removing a test that fails? Literally, test fails, remove it, problem solved. Ship it. Sure there are build warnings, but CI isn't complaining, so..? Is that a valid use case? If your team member did that, you'd be cool-and-the-gang, easy-like-sunday-morning, shaming-is-the-real-shame?
- cuddlecake 5y agoYou're trying to reframe my argument in a bad way. I'm talking about people deciding to use a certain technology with tradeoffs. You're talking about people going against quality standards of a development team. And that's where I end the conversation, you bore me.
- rendall 5y agoNot trying to reframe anything. Just trying to understand the bounds of your ease with team members making these decisions. I haven't been hostile to you or anyone who disagrees with me, by the way. Just trying to understand if and where I'm incorrect. Furthermore, I said what I said in reaction to someone disliking the idea of Svelte being able to use any javascript library at all because of the chaos and bad practice that represents. > You're talking about people going against quality standards of a development team. That's what I've been taking about this whole time