Sree

@chribjel for github, i suggest this mrshu.github.io/github-statuse…

got really tired of trying to find the status page of all services so i made statuspages.dev a directory of status pages so you can find them all in one place. no more searching for the status page all over the place i will open source it soon and accept pull requests for new services

@soohoonchoi ergo cooked

@eersnington jojo characters from non adapted parts lean more technical. Its over for you once sbr drops tho

we've been hiring engineers and some members of our team thinks that anime pfp = signal. this is not always the case so i made them a reference guide.

this is insanely cool

Introducing the Secure Exec SDK Secure Node.js execution without a sandbox ⚡ 17.9 ms coldstart, 3.4 MB mem, 56x cheaper 📦 Just a library – supports Node.js, Bun, & browsers 🔐 Powered by the same tech as Cloudflare Workers $ 𝚗𝚙𝚖 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 𝚜𝚎𝚌𝚞𝚛𝚎-𝚎𝚡𝚎𝚌

@mitchellh big w

Excited to share that I've joined Vercel's Board of Directors. Vercel is made up of builders and tastemakers that continually ship things that deeply impact how developers work: Next.js, AI SDK, v0, etc. I can't think of a more exciting place to be. Let's fucking ship. ▲ My relationship with Vercel goes back to the earliest days. HashiCorp was an early adopter of NextJS and Vercel (~10 years ago!) and it remains my default tech stack and deployment platform to this day. Ghostty's website is all on Vercel, too! Beyond that, I've been continually impressed with the teams relentless focus on shipping meaningful software. And importantly, software that has incredible taste. Now we are in the age of agentic software development. Vercel is building agentic infrastructure that I think every app and agent will need (I certainly need it!) and I can't think of a more exciting place to be. Huge thanks to @rauchg , Jeanne, Marten, @cramforce, @tomocchino and the entire Vercel team for the warm welcome. Time to work.

@dillon_mulroy insane deja vu hit me x.com/RhysSullivan/s…

5.4's idea of cleaning up stuff

the elder nodes

Some updates for 𝚝𝚞𝚛𝚋𝚘 𝚠𝚊𝚝𝚌𝚑: → No longer uses a daemon (much more stable) → Up to 26x faster due to engine improvements → Task Graph instead of Package Graph under Future Flag That last one is particularly exciting. See video, and imagine how this will scale the speed of your repo.

We migrated @v0’s codebase from ESLint + Prettier to Oxlint + Oxfmt by @oxcproject, CI is now 3x faster. Love the OSS ecosystem.

@joshtriedcoding @posthog if you blink at the times it is flickering, it will be a perfectly still dashboard for you

ehm @posthog are you ok 💀

@DavidKPiano @tlakomy angularjs mentioned in 2026

@tlakomy Not since Angular 1.0

I remember everyone (except the core team) telling me how wrong I was when I first gave a talk about useEffect

if you’ve generated a SPEC․md, PRD․md, or PLAN․md and fed it to an agent in the past week, this is mandatory reading so many nuggets of wisdom in here

Whatever your take on this, writing code has always been tremendously easy compared to designing/maintaining large systems. The best engineers in the world are the best because of this stuff. Currently LLMs will not save you from bad architectural decisions. You need to constrain them to do the right thing.

@iamsahaj_xyz @nishimiya beer is non performative matcha for the weekends. both sucks

@nishimiya gotta be beer

what’s something everyone pretends to like but nobody actually enjoys

.@nodejs has always been about I/O. Streams, buffers, sockets, files. But there's a gap that has bugged me for years: you can't virtualize the filesystem. You can't import a module that only exists in memory. You can't bundle assets into a Single Executable without patching half the standard library. That changes now 👇

@acdlite bart loop

I don't know if this actually works but it makes me feel good

@makisuo @EffectTS_ this is how i'm introduced to an oss slack alternative

Migrated Hazel to @EffectTS_ V4 this weekend -8k lines and 500kb less in frontend bundle size LFG

@BenjDicken is it webscale?

Benchmarking Postgres this week. What's on your wish list? I'm particularly interested in: - jit on/off - autovacuum tuning and pg_squeeze - Conn scaling (both with and w/o PgBouncer) - Comparing performance across versions 12-18 - General perf tuning

a dead giveaway for slop PRs opened by claude or openclaw agents that i've noticed is > creates a draft pr > edits in the body later > opens the pr later for review have a gh action that auto closes such PRs until the clankers stop doing this when their training data updates