aev

Advances in the java programming language, version 16 and newer, slashed a million lines of code from my codebase. Maintaining my programs became easier overnight, due to this 1 secret trick: Records. 
Unfortunately version 16 was not LTS, so I had to wait until this year's release of version 21, which is LTS. 
 Go read the linked article. It explains Java Records in a very approachable manner.

Andrez Sainz de Aja writes that comments are a code smell: they make us lazy. Instead of using comments to convey intent, the coding should. But that is hard, so it is easier to write dumb coding and just put the intent into comments.

"You can't prove your value to someone whose business value relies on not seeing it," and other inspirational meanderings by Wachter-Boettcher about the position of UX and design in product development, where designers' livelihood and mental well-being gets threatened by late-stage capitalism.

Wow. Molly Holzschlag passed away. An invaluable force for adoption of web standards and usability. May Molly's loved ones find solace in sharing those memories that inspire them most.

Listen, gain, build, test, query: 5 tips from experience.

Listen.

Observe other interfaces. Study them. Are they intuitive? Are they engaging? Who thinks so? Just you? Your boss? Millions of users? Who are those users? Local people? People like you? Or people from other cultures? People unlike you? More is better.

Gain

Gain examples of intuitive and engaging interfaces in the wild. Determine which of those can be made to fit whatever product or service it is you want users to use, or customers to purchase.

Build

Build the interface. If you’re the designer: don’t worry about coding, storage, security, and payment models. Focus on the components and how they fit into the larger view. Start with pen and paper, then move on to tools like Axure and Figma.

Test

Test how it feels. Does the flow guide you well? Or does it have you bouncing around? Can people who live in other parts of the world, enter their information? Can people who use smaller or larger devices enter information and see what you want them to see? Can people who are blind, or who work in a loud factory, or cannot move very well, also use your interface?

Question

Question your own assumptions. Question why differing people find differing interfaces more intuitive. Why don’t we all simply agree that what I find intuitive is intuitive for everyone?

Rinse and repeat.