
UX/UI product designer. I share #webdesign, #webdev knowledge and #AI adventures. DM's are open.
Houston, TX
Joined May 2010
- Tweets16.9K
- Following753
- Followers950
- Likes11.5K
Try asking AI how a fictional workflow could fail. Then verify the suggestions. A generated edge-case list is a starting point for review, not evidence about real users.
1
A new component isn't an adoption plan. What replaces the old pattern, what could break, and who reviews the change? Migration guidance belongs in the design system too.
3
44
Permission design isn't finished when the button is disabled. Explain the boundary and a safe next step, without exposing restricted information.
6
A spinner says the software is busy. It doesn't explain that a person needs to approve the work. Design the waiting state around the real dependency.
15
“Focus on product and make money the consequence” has to be one of the best advices I have heard.
20
Not every risky action needs another warning dialog. Some need undo. Others need confirmation or a recovery path. I'd separate those decisions before designing the interruption.
10
Translation: At last we got the Adobe Flash we were hoping/craving for.
👍🎯💯
Rive is now a full engine. Most think of Rive as an animation tool, because that’s where the format started, but the goal was always to build a new type of experience engine. Lightweight enough to run in another engine or runtime (like Spotify Wrapped) yet powerful enough to run an entire game.
It’s lightweight, accelerates vector graphics like no other engine or runtime, supports shaders for 3D and effects, and it runs anywhere. It opens up all kinds of experiences not just for the web, but also for native mobile, consoles, underpowered smart TVs, vehicles, and anything else with a gpu.
Royalty free, no rev share, no runtime fee, MIT open-source. No other engine gives you all that with a tiny runtime that can run anywhere.
Luis -Let´s 2026 ⚡️- Suarez retweeted
On October 13, 2000, Steve Krug, a UX designer and information architect, published Don’t Make Me Think. The book deals with web usability and the interdisciplinary field of HCI.
Less clutter helps. Losing context doesn't. A simpler screen can still make the task harder if people must search elsewhere.
8
A cleaner screen isn't always a clearer workflow. What does someone need to know, do next, and keep in view?
13
Great food for thought and topic to discuss.
There’s still time with current AI state of the union.
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
20


















