We're finally shedding the .so (thank you Somalia!), and using the .com for @NotionHQ. And for this beautiful moment, I want to share a fun story:
Back in 2018, I had just joined Notion, and one of the first things @ivan asked me to do was figure out how we could own https://t.co/BxoFvc83VG. I had never done a big domain purchase before, so I reached out to a few domain brokers to understand the landscape. We tried different brokers, kept things anonymous, and attempted to surface a price the seller might consider.
A year went by… nothing. Meanwhile, it was pretty clear this was only going to get more expensive as we grew. We needed a different approach. A fellow founder connected me to a broker who took a very different tack. Less transactional, more long-term relationship builder. He spent months getting to know the domain owner. Turns out owner was a fellow entrepreneur in the west coast… and a huge Grateful Dead fan.
So we figured, why not get creative? Something beyond just price. So I called up our investor Ronny Conway and asked if there was any way he could help set up a private meeting between the domain owner and the Grateful Dead. Ronny is one of those people who somehow makes impossible things possible. A week later he calls me back: “New York City. Halloween. 15 minutes after the concert. Done.”
The broker went back to the owner with an offer: some cash, some equity, and a private meeting with the Grateful Dead. That got his attention. He didn’t take the band meeting in the end, but he did lean into the equity (great call, in hindsight). We shook hands, and a few weeks later, the deal was done.
I’ve been waiting years for the day we move our product to https://t.co/BxoFvc83VG. Looks like 2026 is finally the year. Safe to say I’m unreasonably excited about this update!
"A horizontal agent could in principle build the same learning infrastructure. The reason it doesn't, beyond pure focus, is UX: capturing this kind of knowledge depends entirely on the workflow surfaces you give the user, and vertical players can shape those surfaces around exactly what their workflow needs to surface. Horizontal tools can't."
Great read from @joeschmidtiv, with some strong counterarguments to the "everything will be subsumed" narrative.
“Developer Platform” is a bit of a head fake.
What @NotionHQ’s announced will end up being far more impactful for knowledge work and is beautifully counter-positioned against the labs.
Props to @ivanhzhao, @mschoening, @akothari, and the team. You’re on an epic run!
To the Claude Code team's credit, they've acknowledged this and I'm certain they'll emerge with an elegant solution that threads the needle.
There's one more dimension of complexity (single vs multiplayer) to tackle as they take this on.
https://t.co/9ijOwcL794
You know, we think about this literally 24/7 and I suspect that we’ll figure this out eventually
For now, they offer slightly different flavors to users - chat for easy conversations, Cowork when you want to safely work on something, Code if you’re a developer and want to code with Claude
interrupting my otherwise relaxing sunday to remind everyone that the fact that Claude is incapable of referencing sessions across Chat, Cowork, and Code is an absolute tragedy.
@elithrar Congrats, Matt. Massive release! We’ve been building something similar internally for our use case at @hxtweets and looking at S3 files, but absolutely love to give this a try.
Expanding on this a bit, a product design tool would:
- Allow you to create and visualize your concepts as primitives
- Allow you to see relations between your product concepts
- Allow you to list and prioritize your constraints
- Allow you to maintain competing versions of concepts or relations
- Assist you in understanding impacts or consequences of modifying parts of that system
I've yet to see any tool actually try to do this, but whiteboards/canvas are the closest, as they enable me to map this out freeform.
We might have swung the pendulum a bit too hard though. Agree with @rsms that there's a meaningful place and distinct modes for "exploration" and "production".
https://t.co/J5B2nkPL6L
This is really neat but it’s not a design tool as much as it’s a design _production_ tool.
The practice of design is mostly about what comes before production.
There’s no doubt in my mind that all parts of software production will become automated very soon. Writing code, making web pages, putting pieces of a design system together etc.
And that’s fine. I think few people actually enjoy this kind of production work. Wouldn’t it be better if we spent our precious time in life on what is more meaningful?!
At the core, the practice of design is methodical; like architecture, not like art. In a nutshell: We find constraints, form comprehension of the whole and propose solutions that honor those constraints. First after that do we enter some form of production phase, usually prototypes first, learn about some constraints that were hidden before, loop back, prototype and then build the production-grade “final” artifact.
These last few tasks are quickly losing value because AI tools can do it much faster (not yet better though) than humans. It’s simply just what has the best RoI for a business.
Some companies and individuals will continue to spend human time on certain parts of the “production line” as a market differentiator, but it will cost them a relatively high price compared to competitors.
Anyhow, I still haven’t seen a tool better than Figma that supports the actually-interesting part of the design process.
I wouldn’t be surprised if Figma focused their products on that, maybe separating “products for production” of “products for ideation & exploration.” The latter would obviously still leverage AI, but not to do the work for me but rather to support my efforts the way a therapist helps me live a better life (not living my life for me.)
@elithrar Congrats, Matt. Massive release! We’ve been building something similar internally for our use case at @hxtweets and looking at S3 files, but absolutely love to give this a try.