Other times, however, Copilot is clearly just regurgitating irrelevant code samples that aren’t at all useful. Sometimes, it’s so far off base its suggestions are hilarious. (It regularly suggests that I start my components with about 25 nested divs, for example.)

But if we’re giving one of the world’s major corporations our money, in exchange for this tool that’s supposed to make us better…shouldn’t it be held to some standard of quality? Shouldn’t the results I get from a paid service at least be better than a bad StackOverflow suggestion that got down-voted to the bottom of the page (and which would probably come with additional comments and suggestions letting me know why it was ranked lower)?

As more and more of the internet is generated by LLMs, more and more of it will reinforce biases. Then more and more LLMs will consume that biased content, use it for their own training, and the cycle will accelerate exponentially.

But when I’ve asked blind colleagues what they want from Vision Pro, the conversation almost always moves to the future—not the opportunity to do computing tasks on a head-mounted device or even to watch a movie in the headset. Many blind people want Vision Pro to be an eyesight alternative or assistant, a way to see the world, identifying both the wondrous and the mundane.

It is important to make users aware of required fields upfront. This should prevent them from making submission errors and having to backtrack through a form to fix such errors. But what is the best and most accessible way to indicate required fields? This article aims to explain exactly what’s required.

This is a well-established and widely understood convention but it’s still good practice to include a note at the beginning of the form to explain that asterisks denote required fields.

This should make it clear why there is a reason that the virtual buttons in our graphical user interface should indeed look like buttons: They should commu­nicate that they can be used. When they just look like icons, they don’t do that.

In touch interfaces however, that is often not the case. There, the actual outline of the graphic – let’s say the minus – is often the only thing that can be touched.