3 ms·
> Why would a developer be in charge of testing the user experience from the user perspective? I can count on one hand the number of companies I've worked at i
by josephg 6y ago
> Why would a developer be in charge of testing the user experience from the user perspective?
I can count on one hand the number of companies I've worked at in the last decade who had in-house QA teams. Most companies just rely on the developers to test their (our) own code. The exceptions are banks, gamedev companies and big corp products (like Windows).
Most web software I've seen - especially in the startup world - just assumes that "it works well enough on the developers' specced out mac" means it works. The most tragic version of this I saw was our app looking awful on a ‘normal’ 19” desktop monitor. The problem was our designers did all their work from 27" imacs. They never thought to design and test on smaller displays. Or the designers placing adjacent colors that look great on color graded displays but are almost indistinguishable on the trashy 6 bit TN displays that were ubiquitous in offices a few years ago.
Even in companies with dedicated QA I haven't seen many tickets of the form of "the program runs slowly on this old computer we have". Sadly the creeping performance rot is mostly invisible.
- virtue3 6y agoI worked at an education tech startup so we were mildly aware of our app being run on slowly performing computers. Low bandwith conditions were more of the worry tho. Honestly, people running slow computers are probably just used to poor performance. I fully agree with you that we should do something about it but I don't see that happening unless it's a strong priority (feature X/y/z or performance? is usually the conversation). Anecdotally: I'll never forget the first time I launched an app from an SSD and vowed I was never going back.