The web is a communication medium: having bad delivery is going to impact the efficacy of the message. I've worked as both a developer and a designer, and as a developer I've certainly had to push back against content-focused people requesting things they didn't realize were, frankly, bananas. Tech isn't their job, so it was my job to surface those problems before they arose. However, as a designer, I've also had to push back against developers that refused to acknowledge that technical purity is a means to an end, not an end in itself. Something looking the same in lynx and firefox isn't a useful goal in any situation I've encountered, and the only people that think a gopher resource has better UX than a modern webpage stare at code editors all day long.
No matter who it is, when people visualize how to solve a problem, they see how their area of concern contributes more clearly than others'. It's easy to visualize how our contributions will help solve a problem, and also hard to look past how doing something else will negatively impact your tasks. In reality, this medium requires a nuanced balance of considerations that depend on what you need to communicate, why, and to whom. Being useful on a team requires knowing when to interject with your professional expertise, but also know when it's more important to trust other professionals to do their jobs.
No matter who it is, when people visualize how to solve a problem, they see how their area of concern contributes more clearly than others'. It's easy to visualize how our contributions will help solve a problem, and also hard to look past how doing something else will negatively impact your tasks. In reality, this medium requires a nuanced balance of considerations that depend on what you need to communicate, why, and to whom. Being useful on a team requires knowing when to interject with your professional expertise, but also know when it's more important to trust other professionals to do their jobs.