"The UI for filing bugs is inscrutable and has too many hoops to jump through. No one does anything unless every field has been filed meticulously and there is a clear repro. The designer is ridiculed if the thing isn't actually a bug, is a duplicate, or if it was filed in the wrong place. Front-end bugs are automatically "minor" or "nice to have"s without listening (as there is no loss of functionality, and no data loss)."
"The designer is always responsible for stating how it should work, without being able to say "I am not sure why, but this started feeling off and it's in an important place. Can we investigate?" "This is as designed" is an automatic conversation ender. The tiniest of external reports, social posts, or blog posts, immediately are prioritized higher than in-house experience."
The bug-filing interface is difficult to use and enforces many procedural requirements, inhibiting reports without perfect repros. Designers face ridicule when reports are duplicates, misfiled, or judged not to be bugs. Front-end issues are labeled minor because they cause no data loss, often without being heard. Designers are expected to prescribe correct behavior but lack permission to request exploratory investigation. "This is as designed" frequently ends conversations. External reports get prioritized over in-house experience. Automated purges close long-standing filings without explanation. Engineers rarely log design issues and human acknowledgement is absent.
Read at Aresluna
Unable to calculate read time
Collection
[
|
...
]