QA and SDET has been gutted as a role more or less industry-wide over the past 10-15 years. Nobody in charge cares about quality. Devs doing their own QA is like Boeing doing its own FAA certifications. Even with the best of intentions it's a setup for failure.
Yeah a lot of QA teams weren't the best, but the solution isn't to get rid of them it's to hold them accountable and improve them. But that takes effort and costs money, easier to just cut them and shift more responsibilities onto devs. The results are predictable.
Resources or the care, tbh. FOSS is a big umbrella and a lot of it simply isn't meant for "customers". Some FOSS apps clearly are trying to build a user base, in which case yeah the points this post makes are worth thinking about.
But many other projects, perhaps the majority, that is not their goal. By devs for devs, and I don't think there is anything wrong with that.
Pleasing customers is incredibly difficult and a never-ending treadmill. If it's not the goal then it's not a failure.
If manufacturers in general were serious about improving efficiency they'd stop putting huge heavy wheels on everything, instead of chasing fractions of a percent with overcomplicated and failure-prone door handles.
Side bonus, smaller wheels with taller sidewall tires are more comfortable, less prone to damage, and the tires are cheaper and easier to replace, too!
Not everyone's ears are the same. MKBHD famously does not use Airpods because he can't get them to stay in. I have tried jogging a couple times with Airpods Pro and they pop out every time.
EarPods/AirPods designs assume that you have certain genetic feature on ears called antitragus that hugs the stem with two opposing wings. I looked mine in the mirrors and one of the wings is basically missing altogether, making it not "anti"-ing. Tim Cook visibly has a pair of bulbous ones.
I kind of have different ethnic background than MKBHD, so, it kind of makes me wonder how that design got the shape it got and how it stayed that way.
Me too, the hard part is showing that this slower, more methodical process is more valuable than the flashy, quick shallow approach. And it means I might have to chew on a problem for a bit before delivering anything, even a proposal or design much less a product. But for a longer time scale it does pay off.
Fortunately I've had a few good managers and business partners in my career that recognize the value, but it's far from universal and I sometimes have a hard time communicating it myself in the face of the common move fast agile culture that is so prevalent in most of tech.
Yes, I have also had to have many difficult conversations with managers over the years who were worried that I wasn't going to deliver. All I could do was reassure them that this was my process; it will start slowly but will then accelerate dramatically. Once they've seen it work it gets easier of course!
Honestly I'd love to check bags more often, but it's too frequently an inordinately slow and risky proposition.
I get free checked bags through my preferred airline's credit card, but still almost never do it because it adds so much time and frustration. The number of times I've had to wait an additional hour+ at baggage claim is ridiculous. And I've had bags lost/misrouted a stupid percentage of the time considering how infrequently I check bags. Fortunately never lost for good, but getting your bags days after you arrive is not great.
Even airlines like Alaska that have their "20 minute guarantee" often exceed it but get away with it because to make a claim you have to wait in line at the understaffed baggage office, wasting even more time after late bags. Get real.
If airlines/airports want to incentivize checking bags they need to do more than just make it free, but make it fast and reliable, too.
