Vincent Chan
@storyway.win
Reposted by Vincent Chan
trying to get the highlights of react commit history analyzed into a DAG of decisions and design changes in deciduous, it’s chugging along
January 5, 2026 at 7:16 PM
trying to get the highlights of react commit history analyzed into a DAG of decisions and design changes in deciduous, it’s chugging along
Reposted by Vincent Chan
the hack to being productive with claude code is to start the project with great e2e tests that are declarative enough that they let you precisely specify behavior without saying too much
it's really magic
it's really magic
January 8, 2026 at 11:37 PM
the hack to being productive with claude code is to start the project with great e2e tests that are declarative enough that they let you precisely specify behavior without saying too much
it's really magic
it's really magic
Reposted by Vincent Chan
haven't found anything so i made my own
January 9, 2026 at 1:55 AM
haven't found anything so i made my own
Reposted by Vincent Chan
is there any open source skill benchmark workbench for claude code?
i want to define multiple versions of a skill, acceptance criteria (to be evaluated by a separate agent), and a runner that does repeated runs of different versions of my skill to see if there’s a statsig improvement in any version
i want to define multiple versions of a skill, acceptance criteria (to be evaluated by a separate agent), and a runner that does repeated runs of different versions of my skill to see if there’s a statsig improvement in any version
January 8, 2026 at 1:33 PM
is there any open source skill benchmark workbench for claude code?
i want to define multiple versions of a skill, acceptance criteria (to be evaluated by a separate agent), and a runner that does repeated runs of different versions of my skill to see if there’s a statsig improvement in any version
i want to define multiple versions of a skill, acceptance criteria (to be evaluated by a separate agent), and a runner that does repeated runs of different versions of my skill to see if there’s a statsig improvement in any version
Reposted by Vincent Chan
why am i working on this?
well i think part of the reason LLMs don't do a great job in complex brownfield projects is because they don't understand past design choices and constraints that aren't directly expressed in code
so i'm wondering if making those queryable can help. it helps humans!
well i think part of the reason LLMs don't do a great job in complex brownfield projects is because they don't understand past design choices and constraints that aren't directly expressed in code
so i'm wondering if making those queryable can help. it helps humans!
January 12, 2026 at 3:23 AM
why am i working on this?
well i think part of the reason LLMs don't do a great job in complex brownfield projects is because they don't understand past design choices and constraints that aren't directly expressed in code
so i'm wondering if making those queryable can help. it helps humans!
well i think part of the reason LLMs don't do a great job in complex brownfield projects is because they don't understand past design choices and constraints that aren't directly expressed in code
so i'm wondering if making those queryable can help. it helps humans!
Reposted by Vincent Chan
ok this is amazing
i've made a claude skill that uses @bobbby.online's deciduous to generate a design evolution tree from a project's commit history. this tree is generated by Claude using the displayed prompt (and my skill). the graph ~matches how i remember it
react-deciduous-example.pages.dev
i've made a claude skill that uses @bobbby.online's deciduous to generate a design evolution tree from a project's commit history. this tree is generated by Claude using the displayed prompt (and my skill). the graph ~matches how i remember it
react-deciduous-example.pages.dev
January 12, 2026 at 3:11 AM
ok this is amazing
i've made a claude skill that uses @bobbby.online's deciduous to generate a design evolution tree from a project's commit history. this tree is generated by Claude using the displayed prompt (and my skill). the graph ~matches how i remember it
react-deciduous-example.pages.dev
i've made a claude skill that uses @bobbby.online's deciduous to generate a design evolution tree from a project's commit history. this tree is generated by Claude using the displayed prompt (and my skill). the graph ~matches how i remember it
react-deciduous-example.pages.dev
Reposted by Vincent Chan
lmao claude code just deleted my entire project in yolo mode and i had no backup
January 12, 2026 at 12:49 PM
lmao claude code just deleted my entire project in yolo mode and i had no backup
Reposted by Vincent Chan
i made a thing:
npx woodshed
npx woodshed
January 13, 2026 at 2:23 AM
i made a thing:
npx woodshed
npx woodshed
Reposted by Vincent Chan
digging through old react commits, my favorite titles so far
January 6, 2026 at 1:19 PM
digging through old react commits, my favorite titles so far
Reposted by Vincent Chan
Facebook's Static Hermes is kind of incredible. It can compile JavaScript into C, which is then optimized into native machine code.
I just compiled the Less.js source code into a C library. Then I called it from Rust as a native Parcel plugin (no Node). Wild. 👨🔬
devongovett.me/blog/static-...
I just compiled the Less.js source code into a C library. Then I called it from Rust as a native Parcel plugin (no Node). Wild. 👨🔬
devongovett.me/blog/static-...
How to compile JavaScript to C with Static Hermes
Lately, I've been working on porting more of Parcel to Rust, and investigating ways to embed JS-based plugins. This post describes how I used Static Hermes to compile Less.js to a native C library tha...
devongovett.me
December 29, 2025 at 10:30 PM
Facebook's Static Hermes is kind of incredible. It can compile JavaScript into C, which is then optimized into native machine code.
I just compiled the Less.js source code into a C library. Then I called it from Rust as a native Parcel plugin (no Node). Wild. 👨🔬
devongovett.me/blog/static-...
I just compiled the Less.js source code into a C library. Then I called it from Rust as a native Parcel plugin (no Node). Wild. 👨🔬
devongovett.me/blog/static-...
Reposted by Vincent Chan
not sure this makes sense but it tickled my brain, yall should read it
December 31, 2025 at 8:45 AM
not sure this makes sense but it tickled my brain, yall should read it
Reposted by Vincent Chan
if you're writing your post with AI, i'm not reading that shit to the end. not because i hate AI but because it's just not good enough. if i can spot it, it's skill issue both on your and AI part
January 5, 2026 at 2:27 PM
if you're writing your post with AI, i'm not reading that shit to the end. not because i hate AI but because it's just not good enough. if i can spot it, it's skill issue both on your and AI part
Reposted by Vincent Chan
December 25, 2025 at 9:03 AM
Reposted by Vincent Chan
i actually don’t get this attitude.
even if there’s a winning wiring of smarts and duct tape, clearly it’ll take a few months for someone to package it up in a product. then competition will sort it out, then open source will copy it half-badly, then it will git good.
why bother w/ middle steps?
even if there’s a winning wiring of smarts and duct tape, clearly it’ll take a few months for someone to package it up in a product. then competition will sort it out, then open source will copy it half-badly, then it will git good.
why bother w/ middle steps?
Andrej Karpathy is worried about keeping up with software engineering practices
December 27, 2025 at 10:38 AM
i actually don’t get this attitude.
even if there’s a winning wiring of smarts and duct tape, clearly it’ll take a few months for someone to package it up in a product. then competition will sort it out, then open source will copy it half-badly, then it will git good.
why bother w/ middle steps?
even if there’s a winning wiring of smarts and duct tape, clearly it’ll take a few months for someone to package it up in a product. then competition will sort it out, then open source will copy it half-badly, then it will git good.
why bother w/ middle steps?
Reposted by Vincent Chan
the funniest thing about "this is not AI, this is machine learning and it's good!!!" replies is that ML is a subfield of the broader AI field, and the disliked "AI" is a product of that exact subfield
Today, we're rolling out a new suite of AI-driven global weather models, including a "first of its kind" hybrid ensemble system! Want to get geeky with us? Come check it out:
www.noaa.gov/news-release...
www.noaa.gov/news-release...
This AIGFS forecast in the form of a map, for December 10, 2025, shows the heavy precipitation from an atmospheric river hitting the U.S. Pacific Northwest. AI weather models like this one will protect life and property by improving forecast accuracy and timeliness for events such as the catastrophic flooding that impacted the Northwest.
www.noaa.gov
December 18, 2025 at 5:40 AM
the funniest thing about "this is not AI, this is machine learning and it's good!!!" replies is that ML is a subfield of the broader AI field, and the disliked "AI" is a product of that exact subfield
Reposted by Vincent Chan
in case you missed it: yesterday i wrote about a new open source tool i made, called RSC Explorer.
it lets you interactively step through how the React Server Components protocol works directly in the browser — no server needed.
it lets you interactively step through how the React Server Components protocol works directly in the browser — no server needed.
i wrote about my new hobby project overreacted.io/introducing-...
Introducing RSC Explorer — overreacted
My new hobby project.
overreacted.io
December 19, 2025 at 7:10 AM
in case you missed it: yesterday i wrote about a new open source tool i made, called RSC Explorer.
it lets you interactively step through how the React Server Components protocol works directly in the browser — no server needed.
it lets you interactively step through how the React Server Components protocol works directly in the browser — no server needed.
Reposted by Vincent Chan
thanks to claude code i might actually ship the thing i wanted to make back in 2021 but didn't have the patience for. incredible time for people with vision and skill but low execution velocity
December 22, 2025 at 3:02 PM
thanks to claude code i might actually ship the thing i wanted to make back in 2021 but didn't have the patience for. incredible time for people with vision and skill but low execution velocity
Reposted by Vincent Chan
since there's much interest in the RSC protocol, i made a little debugger tool that runs entirely in the browser (no server).
would anyone find it useful?
would anyone find it useful?
December 13, 2025 at 11:18 AM
since there's much interest in the RSC protocol, i made a little debugger tool that runs entirely in the browser (no server).
would anyone find it useful?
would anyone find it useful?
Reposted by Vincent Chan
made a thing rsc-playground.pages.dev
RSC Playground
rsc-playground.pages.dev
December 14, 2025 at 1:19 PM
made a thing rsc-playground.pages.dev
Reposted by Vincent Chan
deployed big update to rsc-playground.pages.dev
lots of bugfixes and a few new examples.
this basically works now! i'll open source a bit later
lots of bugfixes and a few new examples.
this basically works now! i'll open source a bit later
December 15, 2025 at 8:08 PM
deployed big update to rsc-playground.pages.dev
lots of bugfixes and a few new examples.
this basically works now! i'll open source a bit later
lots of bugfixes and a few new examples.
this basically works now! i'll open source a bit later
Reposted by Vincent Chan
RSC Explorer is now open source! tangled.org/danabra.mov/...
danabra.mov/rscexplorer
A tool for people curious about the React Server Components protocol
tangled.org
December 16, 2025 at 10:00 AM
RSC Explorer is now open source! tangled.org/danabra.mov/...
Reposted by Vincent Chan
cool news, sidetrail.app is now open source on @tangled.org!
the stack:
- atproto (jetstream + new lex client)
- next 16 + cacheComponents (yes, a recent version)
- postgres + drizzle, redis
- vitest
the stack:
- atproto (jetstream + new lex client)
- next 16 + cacheComponents (yes, a recent version)
- postgres + drizzle, redis
- vitest
danabra.mov/sidetrail
an app to share curated trails
tangled.org
December 5, 2025 at 7:24 PM
cool news, sidetrail.app is now open source on @tangled.org!
the stack:
- atproto (jetstream + new lex client)
- next 16 + cacheComponents (yes, a recent version)
- postgres + drizzle, redis
- vitest
the stack:
- atproto (jetstream + new lex client)
- next 16 + cacheComponents (yes, a recent version)
- postgres + drizzle, redis
- vitest
Reposted by Vincent Chan
i finally fixed caching! (i think)
did -> handle, handle -> did, and did -> avatar lookups should all be getting cached in redis now which should considerably speed up navigations and stop 1s+ load times on some pages
cause was fun: github.com/vercel/next....
did -> handle, handle -> did, and did -> avatar lookups should all be getting cached in redis now which should considerably speed up navigations and stop 1s+ load times on some pages
cause was fun: github.com/vercel/next....
Docs: [Cache Components] "use cache" pitfalls with map() · Issue #86896 · vercel/next.js
What is the documentation issue? Here's a fix I'm going to deploy now: const resolveDidToHandle = cache(async function resolveDidToHandle(did: string): Promise<string> { "use cache: redis"; tagDid(...
github.com
December 6, 2025 at 9:22 AM
i finally fixed caching! (i think)
did -> handle, handle -> did, and did -> avatar lookups should all be getting cached in redis now which should considerably speed up navigations and stop 1s+ load times on some pages
cause was fun: github.com/vercel/next....
did -> handle, handle -> did, and did -> avatar lookups should all be getting cached in redis now which should considerably speed up navigations and stop 1s+ load times on some pages
cause was fun: github.com/vercel/next....
![A side‑by‑side code comparison showing migration from TypeScript path aliases to Node.js imports. On the left, tsconfig.json defines `"paths": { "@/ *": ["./ *"] }`, used as `import "@/foo"`. On the right, package.json defines `"imports": { "#app/ *": "./ *" }`, used as `import "#app/foo"`. Red arrows point from the TS config to the package.json config and from the old import style to the new one.](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:eaimln3uk5ntgmykcbxrmsyp/bafkreigvvdln7epnz7iuxiz4ky5blyc7vh4o6gmxqt6ju32cnhlicbsmva@jpeg)
Reposted by Vincent Chan
x.com/panchito built a _really_ slick looking Github file viewer clone that fully uses RSCs and new React features, as well as making smart use of modern CSS. Great writeup on the implementation:
wtbb.vercel.app
I tried browsing the React repo example and it's _fast_! Really impressive!
wtbb.vercel.app
I tried browsing the React repo example and it's _fast_! Really impressive!
Without the blue bar
a github clone with NextJS 16 and cache components
wtbb.vercel.app
December 4, 2025 at 8:39 PM
x.com/panchito built a _really_ slick looking Github file viewer clone that fully uses RSCs and new React features, as well as making smart use of modern CSS. Great writeup on the implementation:
wtbb.vercel.app
I tried browsing the React repo example and it's _fast_! Really impressive!
wtbb.vercel.app
I tried browsing the React repo example and it's _fast_! Really impressive!