"Because that's stupid" is not a valid reason for closing out bugs.

 

Title: But what if that was the justification for building the feature in the first place? 
Snarky: "Because that's stupid" is not a valid reason for closing out bugs.


The product manager/developer relationship is inherently tense in my experience. I think it's because developers, ahead of the technological curve when it comes to building software products,  recommend features that go over like a lead balloon when pitched to the product team.   Not being the 'business' experts in the organization, they are then left to implement what in their minds are inferior or *gasp!* obsolete solutions.

Having then to go back and fix bugs in said features (arguably, their own fault),  it can be hard to resist adding a few snarky comments in the bug tracker.