How many tokens?
UI and math time! UI = f(props) is the most famous line in React. But that f is JavaScript, not math.
Inspired by @_chenglou’s Handwired project, I compiled a <Dashboard/> component into a real math function, and asked what becomes possible.
calculus-of-interfaces.verce…
1
35
Set this up for me @bot
Want to know the latest in @bot?
I made a What's New Bot:
- Checks x.ai/bot/changelog each day
- Checks my latest what's new video
Delivers it straight to your chat
Get it here: x.ai/bot/dEFFB5_KX5U06lNJWVZ…
3
8
3,471
first time trying out @claudeai Projects. Not a good experience. It started 2 threads in parallel: design & implementation. Each did their own thing, it was a total mess. Nobody in his fucking right mind would design and implement in parallel LMFAOOO
36
the product I'm working on is so fast that the designers don't even bother designing loading states🗿🗿🗿
1
2
297
Suspense makes coordinating loading states a breeze. The use() stuff is still PITA though. Was hoping something more higher level built in to react
Replying to @denCual @aurorascharff
I can see how it seems like a reversion, but here's how to reconcile it.
Two principles of Suspense: 1) Streaming is good 2) Unintentional loading states are bad
With Suspense, we will never show you a loading state that you did not explicitly define. In the extreme case, you can omit Suspense entirely and wait for the entire page to buffer.
However, the ideal user experience is almost never to block. You want to be able to show some kind of instant loading state that was loaded by the app ahead of time.
It's possible under extreme conditions that the loading state itself isn't available. In which case, React will suspend. So we will still block in the worst case, but you typically want to do whatever you can to avoid that from happening. That's what Instant Navigations in Next 16.3 is all about.
In our early Suspense communications, we over emphasized the ability to block because that was the novel capability that didn't exist in other frameworks. But streaming is still good.
Here's an example from a different domain: Consider a streaming video. It's a terrible experience when the network is slow and the feed buffers. Services will do their best not to block the stream, e.g. by falling back to a lower resolution. However, at a certain point, it's better to just buffer until the network catches up. That doesn't mean buffering is ideal, but it's a better worst case experience than, say, showing an incomplete frame.
2
364
Can it run next js
Run Docker inside Vercel Sandbox.
▪︎ Build and run containers in full isolation
▪︎ Persist installs and images across sessions
▪︎ Run databases, test suites, or full apps
vercel.com/changelog/run-doc…
42
Raibima Putra retweeted
How to make your engineering job application stand out (from the perspective of someone looking at hundreds of resumes):
1. Your resume should be one page. If you really need more space, link to a website. You don't need 10+ bullets for each job.
2. You will immediately stand out >90% of applications if you link a personal website that has some intentionality behind it.
3. If you are going to link your X, you might want to clean up your posts? Seems obvious but... people post some wild stuff.
4. You should link your GitHub. Please avoid doing a profile README that looks like a MySpace profile with the badges and images. I'm trying to look at code and your ability to build interesting ideas.
5. You should try to customize your application to the company. If you're applying to a startup, the courses you took in college probably don't matter as much. Maybe more if you're trying to make it through the ATS screening for FAANG.
6. I'm seeing a surprising number of resumes which don't talk about AI or agents at all. Software engineering is changing and it's a pretty fair assumption that you will be expected to learn or understand coding with AI for your job. That should be reflected on your resume and projects (and I'm not just saying this because I'm at Cursor).
7. Take your LinkedIn seriously. Most devs are here hanging out on X but surprisingly still most people will send around your LinkedIn internally.
8. Find ways to show your unique strengths/tastes/interests. It's nice to see people are smart, well-rounded, and thoughtful. Maybe this is a collection of books you enjoyed and why. Or some writing you've done. Or films you liked. At the end of the day, people want to work with other people they like and respect. If nothing else, it will be a good conversation starter ("oh I love [book] as well!").
9. Do not use AI to write your cover letter or resume text. It's incredibly obvious, especially if you are applying to an AI company. You can still use it to ideate on ideas or phrases, but write it by hand (don't fall victim to the overused in-the-distribution-AI-phrases). See: /humanizer skill.
10. No photos on resumes. Save those for whatever you link out to.
11. Quality over quantity. 3 really good, thoughtful, detailed, interesting projects versus a wall of 27 AI-slop ones.
Remember that hiring managers / recruiters are getting hundreds or thousands of applications for a role. They're not going to spend 20 minutes on every single application. You need to cut the cruft and get to the point. I hope this helps you stand out!
Tried @cursor_ai Glass -- didn't like it one bit.
Bias alert: I'm a code-first guy. The moment the editor UI feels second-class, I'm out.
73
Can’t help but notice Seb’s absence - does he still work on Next / React?
Next.js 16.2
• Up to ~60% faster rendering
• Up to ~400% faster 𝚗𝚎𝚡𝚝 𝚍𝚎𝚟 startup
• Server Function 𝚍𝚎𝚟 logging
• Redesigned error page
• Better hydration errors
• 𝙴𝚛𝚛𝚘𝚛.𝚌𝚊𝚞𝚜𝚎 display in error overlay
nextjs.org/blog/next-16-2
134
I had fun vibe coding the past few days. I may have something launching in a few weeks -- stay tuned.
+ Cursor's "Debug" agent is so gddddd omg
1
53
This is the way
Fun Fact: Stripe does logging differently. They take a super interesting approach to log processing, something that helps them debug production issues faster, cheaper, and with far less complexity.
Logging data belonging to one request is typically dumped across multiple lines. Stitching together these fragmented logs became a pain as they scaled. So what they do is emit a single, comprehensive log line at the end of every request, and they call it the Canonical Log Line.
I just published a video dissecting their entire process and the exact steps they took to implement canonical log lines without breaking their existing log processing systems.
Give it a watch.
It is a pretty short video, but interesting and fun. Something you can implement at your workplace right away.
42
Raibima Putra retweeted
Cursor is a better DX, if you care about code quality.
Claude Code is better if you don’t.
On Cursor vs Claude Code
Fascinating dynamic: engineers are cancelling their Cursor subscriptions and switching to Claude Code/Codex -- but Cursor continues to grow revenue as it's gaining totally new, first-time-AI-user customers.
Is Cursor screwed in this dynamic? Does everyone end up switching to Claude Code/Codex in the long term?
I used to think so, but I no longer do. Claude Code isn't winning because of Claude: the same models are available in Cursor. The most significant thing about the launch of Claude Code around this time last year was that it presented a different, slightly contrarian interaction pattern for engineers: getting back into the terminal. It turns out, this just works much better than using a VSCode-style IDE.
Competition here isn't really about coding models, it's about interaction patterns! The models will continue to compete tightly and be generally available. All the differentiation is in Developer Experience + Brand.
Therefore, the key question is whether new, better interaction patterns are possible. Another way to frame it: is the Claude Code-style UI the best possible UI/UX for this task? I don't think so. It's pretty good, but it's not the end of innovation.
And you might say that it should be hard for a new interaction model to take market share -- but that's exactly what Claude Code did.
I hear that Cursor is going all-in on building their own coding models, but I doubt that's the right move. To me, the big room is in interaction patterns: building better harnesses that provide a better developer experience. I'd expect to see some competition here over the next year or so. Perhaps we'll see another competitive leapfrog, like how Claude Code did in March 2025.
The migration story for @nextjs cacheComponents: flip a global switch to break everything, then 'use cache' your way back to sanity one function at a time... classic
39















