Get it shipped — building better relationships with Devs
This advice works both ways:
- Collaboration
- Communication
- Respect
This advice works both ways:
- Collaboration
- Communication
- Respect
I don’t run analytics on this website. I don’t care which articles you read, I don’t care if you read them. I don’t care about which post is the most read or the most clicked. I don’t A/B test, I don’t try to overthink my content.
Same!
Vitaly provides some sensible rebuttals.
It looks like it will be a great tool for prototyping. A tool to help developers that don’t have experience with CSS and layout to have a starting point. As someone who spent some time building smoke and mirrors prototypes for UX research, I welcome tools like this.
What concerns me is the assertion that this is production-grade code when it simply is not.
Go spelunking down the archives to find some lovely graphic design artefacts.
Another great talk from Simon that explains large language models in a hype-free way.
In the fullness of time, the files you create are more important than the tools you use to create them. Apps are ephemeral, but your files have a chance to last.
Gosh! And I thought I had strong opinions about markup!
A false sense of security persists surrounding digitized documents: because an infinite number of identical copies can be made of any original, most of us believe that our electronic files have an indefinite shelf life and unlimited retrieval opportunities. In fact, preserving the world’s online content is an increasing concern, particularly as file formats (and the hardware and software used to run them) become scarce, inaccessible, or antiquated, technologies evolve, and data decays. Without constant maintenance and management, most digital information will be lost in just a few decades. Our modern records are far from permanent.
Some really interesting long-term thinking from Matt—it’ll be interesting to see the terms and conditions.
A great reminder of just how much you can do with modern markup and styles when it comes to form validation. The :user-invalid
and :user-valid
pseudo-classes are particularly handy!
Time capsules on the moon, using NanoFiche as the storage medium.
Clicking through these cold war slides gives an uncomfortable mixture of nostalgic appreciation for the retro aesthetic combined with serious heebie-jeebies for the content.
The slides appear to be 1970s/1980s informational or training images from the United States Air Force, NORAD, Navy, and beyond.
This is a really clear, practical, level-headed explanatory talk from Simon. You can read the transcript or watch the video.
- No shared (and contextual) sense of purpose
- Overbuilding, or scaling too early
- Inability to make decisions and move forward quickly
- Lack of clear ownership and dedicated resources
- Lack of cultural alignment
The common thread among these issues is that none are related to technical or tooling decisions —or even to the components themselves.
I’m not down with Google swallowing everything posted on the internet to train their generative AI models.
- Be skeptical of PR hype
- Question the training data
- Evaluate the model
- Consider downstream harms
- Good design works for everyone
- Good design makes things obvious
- Good design puts users in control
- Good design is lightweight