I love making diagrams like this, it helps a lot to explain technical details and make people create a better mental map of the problem as you explain.
I'll share some I've made over time!
BREAKING: Ray Dalio just said the AI market is a bubble and it will burst.
"All great technology changes produce bubbles," Dalio told Bloomberg. "The pricking is the converting of wealth into money" right now, every major tech company is pouring hundreds of billions into AI infrastructure and booking it as investment.
The moment investors demand actual returns, companies will have to show that the money spent is generating real profits from real customers. If the revenue is not there, valuations collapse and right now, the revenue is not there.
AI companies are spending $800 billion in capital expenditure this year alone. OpenAI spends $60 billion annually on cloud infrastructure against $25 billion in actual revenue.
Less than 1% of executives globally report meaningful ROI from their AI investments. 95% of enterprise AI pilots have failed to deliver measurable returns according to MIT.
The entire $2 trillion cloud backlog held by Microsoft, Oracle, Google, and Amazon is anchored by two unprofitable companies: OpenAI and Anthropic.
By 2030, the industry needs $2 trillion in annual revenue to justify what is being built today. Bain estimates it will fall $800 billion short.
Dalio is not saying the technology is fake. He is saying the economics do not work yet and every bubble in history has ended the same way when that moment of reckoning arrived.
A common dynamic I observe with AI: it feels most impressive when you don’t know much about the subject, don’t care or don’t have a clear idea of what the you want.
This applies across design, code, legal, and more. If I don’t know code very well, every piece of code it writes feels very impressive.
Once you know what something should feel or look like, it becomes almost impossible to guide AI there. And you definitely can’t one-shot it.
non-designers who have never designed anything: "designers are cooked!"
people who have worked in code, want to work in code, always will work in code: "future of design is code!"
companies selling tokens: "move that button 4px with a prompt!"
designers:
Non-technical types think engineers just “translate” specs into code but that is not how great products are built. PM/design/engineering must work together throughout the process. Throwing stuff over the wall doesn’t work. The best ideas don’t come from the top down, they come after building and experimenting and understanding what’s technically possible. Simply replacing engineers with AIs that do only what you tell them is not a recipe for success.
Introducing the new React Aria docs! 🎉
All-new content and search experience. Interactive CSS and Tailwind examples to get you started quickly – just install with shadcn. New guides and full example apps. MCP server and AI integrations.
Check it out! https://t.co/2LlQw8stZl
"same patterns, the same flows, the same ideas repeated across different tools and teams."
This is what I'm actually afraid of. When we start treating designers as code jugglers, and we start to see even more standardization in the space because everyone is building with the same primitives. Like why try to design or invest in designing something great when you can design and implement something standard in the same timeframe. This is the cookie cutter house of software design.
The more systematic designs tools are, they more systems will suffocate designers. Low fidelity, high fidelity, prototypes, code, all are tools and useful, but none of them is the end. Design is about exploring the problem space, finding a form. The code is kind of unnecessary in that process. Once you get to testing, prototyping or validating stage, the code are useful, because you're trying to refine and make the form to reality.
People are somehow obvious to the double diamond design process and that it exists there for a reason. When you jump in to the validation and implementation directly or try to collapse this in a single diamond, you lose something in the process.
These tools can be great for validating or prototyping the design explorations. So it's part of the process but not the whole process.
New post 🎉
Going back to my roots on writing about the inner workings of things, a breakdown of key-value databases and how you might make one from scratch:
https://t.co/Dpy0TGQpZO
🚨 PSA: iOS 26 Safari breaks modals using position: fixed.
Safari clips fixed elements to the "inner" viewport (even with negative position), which means the backdrop will not extend behind the status bar or address bar.
See next tweet for how to fix this. 👇
Everyone’s racing to invent new AI products.
But an underrated opportunity is just rebuilding apps with insane, never-before-seen levels of polish ... because you can now.
This is super cool. I’m building something similar, but a bit more complex: a Markdown stream with live diffing inside an editor. Haven’t really seen anything like this for AI yet. Will share more soon 👀
I'm writing up a blog post about Markdown streaming, because I think it is an interesting topic.
I reckon there will be almost a dozen people who agree with me!
I don’t get why most companies integrating AI into their products are just adding a chat window. Why not use their own product’s UI to integrate AI? Feels like we’re still not exploring new, non-chat visual interfaces for AI.
Have yet to see any real AI-native UI beyond a text box, chat or mind map
It feels like we’re at the first step in UI design
Most are the same as incumbents just with worse cap tables and better videos
Anything interesting out there?
New React Aria release!
📜 Infinite scroll in ListBox, GridList, Table, and Tree
⚛️ React 19 actions automatic form reset
🐲 Virtualized Tree drag and drop
🤝 Opened API to DOM events – improved integration with other libraries
📆 DatePicker autocomplete
🚀 And TONS more!
It's finally here! Untitled UI React is live ✨
Untitled UI React is the world’s largest collection of open-source React components built with Tailwind CSS v4.1 and React Aria.
Just copy, paste, and build. 👇
@pqoqubbw I recommend using not only the Mac screen reader but also using NVDA on Windows. There is a lot of inconsistency between screen readers across operating systems, using tools like axe alone does not solve real use cases.