There should be exactly one programming language.
One linter for code (performance) and custom ones for each human (accessibility).
Generating components with AI is nice, but what are you going to do with your hundred perfect websites is all that matters.
The refreshed azure tones in canary devtools... alleviate my transient sense of discontent.
By abstaining from capitalizing my prompts, I am simultaneously aiding and impairing the proficiencies of both myself and my machine.
Race against time in a schema-building game that tests your quick thinking abilities.
By intentionally keeping the plus icon right on people’s faces [on a simple interface like Threads], they’re de facto agree that engagement is more important than usability.
This new emerging pattern where you have to scroll the feed upwards to see the menu? Has to die.
Nested CSS is a code smell.
It’d cool if models would come with a source map too.
Finding balance - and alternating - between scaling design vertically and horizontally is key for shipping great products.
TIL there is a rail bird named Sora—Porzana carolina.
Hello from ios?
Tooltips are always an afterthought.
A scrolling behavior different from the native ones is inaccessible by default.
Building backend is obsolete, the future is research and interfaces. Meaningful research can't be predicted and any kind of novel interface will be still based on human feedback.
We'll eventually put AI generated pictures in museums too—but art is the person making it, the road to get there and the possibilities it opens for others. Never the tools.
For visual systems it's incredibly important to keep exposed surfaces at the bare minimum.
Just setting up my twitter.
jk, this is private.