Well, presumably the page's intended audience is software developers at Apple. As a software developer myself, I am all too familiar with the unnecessary churn caused by vague bug reports. It saves time when people include details like error messages (when applicable), steps to replicate, expected result vs. actual result, etc.

Besides, users and developers don't always use software the same way, have the same settings, follow the same forums.

This just feels so backwards. Yes, I know recreating ambiguous issues is annoying because it’s a lot of work, but it’s also our job.

Reminder: we are asking users to give us money in exchange for software.

It’s our job to deliver that working software. It’s not the user’s job to hold our hands and pep talk us into fixing problems. Users can and should find another product that will just do it for them without the whining.

I think the real point of the website, besides joking around, is poking fun at the broke state of the software industry where a bunch of whiny developers and managers will make a million tired excuses for why their software doesn’t just work.

Highlighting bug report and bureaucratic process in response to “your keyboard is jank” is exactly the mindset we need to change.

The point isn’t to start a forum or technical conversation with Apple devs. The point is to laugh at them because their software sucks and “just one more Jira ticket” isn’t going to fix it.

Then again, sometimes a big feature is so comprehensively broken that it’s hard, from the outside, to break it down into specific flaws. Even if you can reproduce the complex circumstances where they manifest.

In the case of the iOS keyboard, I remember one bug that made the rounds (in the popular press!) after somebody recorded their typing in slow motion to validate it [0]. Once they documented it, everybody recognized the feeling and felt vindicated; but it took actual work to substantiate.

That’s the work it seems that Apple engineers should be doing. They have the telemetry, the source access, the design documents, the labs, and the time in their day to make a comprehensive study of it. Just as I can say “my car is handling funny around turns” and let it be the mechanic’s job to diagnose what’s wrong in mechanical terms.

There was a time when this humane aspect was Apple’s particular magic: engineering beyond technical requirements to the point of simplicity, ergonomics, “it just works”…

[0] https://www.macworld.com/article/2952872/heres-proof-that-th...

This isn't a bug report.

Do you honestly think that the developers working for apple looks at the "keyboard experience" and thinks "yeah this is good"? Of course, not. They are competent developers.