The hospital information system Millenium from Oracle was bought by two regions in south of Sweden for around 400 million USD. It turned out to be unusable for Swedish healthcare and had to be shut down after just three days. Actual users of the software (doctors and nurses) were not involved in the procurement.
For group chats in Microsoft Teams with more than seven participants, if you click on "View and add participants" (an icon with two people and a plus sign) you see a list of seven participants. At first I didn't know that you could scroll in this list.
Why don't we instead focus our energies on the user. For some very important software applications the customer is not the user. Let the sales department focus on the customer.
Something that would be useful in my case is a monitor stand stand. Does anyone know why almost no current monitor can be raised so that the upper edge is at eye level? Is it due to incompetence among the current breed of designers? Quite a few of my colleges have a stack of books beneath the monitor stand.
The argument in the article was that the for loop is (potentially) "lying" and that is still true in my example. Niklaus Wirth's Modula-2 had a LOOP statement in which an EXIT statement could occur anywhere. That statement was at least not misleading. In Wirth's last revision of his last programming language Oberon the loop statement is removed and return is no longer a statement but a clause at the end of a function procedure. This makes Oberon a purely structured language.
"universal access to a large universe of documents"
It's a sad fact that a large part of the web doesn't work without Javascript, a technology which enables privacy-invasive practices (and surveillance capitalism). It wasn't as bad when progressive enhancement was the norm.
It's also worth noting that a customer is not necessarily a user. As a developer I don't care so much about the customer but I care wholeheartedly about the users.
In the best scenario the developers are also active users of the software they produce. Then a design flaw or an error that affects the users will also affect the developers and will (hopefully) motivate the latter to correct it.