i3dly

Enjoyer of @Cloudflare Workers. Building tools for developers:
⚡ - Real-time APIs
💻 - Code templates

[i3dly @i3dly_dev]

If your question didn't give you that specific signal you were looking for, reassess the value of that question. Iterate on your interview to optimize false positive/negative rates of new hires.

[i3dly @i3dly_dev]

Technical interviews are hard because interviewers don't know why they're asking the questions they're asking. The goal of interviews should be to reduce false positives/negatives. Each question you ask should have the goal of extracting very specific signals from your candidate.

[i3dly @i3dly_dev]

Hot take: Every programmer should go through a "functional programming is king" phase. At least for some time.

[i3dly @i3dly_dev]

I built a thing to help me build and launch products way faster: https://t.co/YuUZKQrzQ6.

If you've got a new product you're excited to build, but hate building the same baseline of necessary crap that every app needs, come check us out:

https://t.co/Gs3EOuoKSS

[i3dly @i3dly_dev]

I've spent the last few days migrating my pages to workers and chasing down errors. At long last, the site seems stable. But looking at the dashboard gave me a pause. Why is this number in red? @Cloudflare

[i3dly @i3dly_dev]

Woo! We're back online! https://t.co/dYaEd6pc1W

[i3dly @i3dly_dev]

As https://t.co/VFsrz0wPhC is backed by SQLite-backed Durable Objects, our service is currently affected by Cloudflare's broad service outage. Will post here when we're back up and running. Apologies for the inconvenience.

[i3dly @i3dly_dev]

🚀 https://t.co/VFsrz0wPhC 3.2 is out!

⚡ Prebuilt Live Components via the @shadcn CLI
🔧 CRDT stability fixes in @Cloudflare Workers

Build collaborative apps with less friction → https://t.co/eDonP4QGSo

#pluvio #realtimedev #shadcn

[i3dly @i3dly_dev]

🚀 https://t.co/h17BjQYeC5 3.0 just dropped!

This release is all about making it easier for developers to get started.

✅ Rich text editor support (Yjs provider now available)
📘 Revamped documentation for a smoother DX
💸 A new free tier to try the https://t.co/h17BjQYeC5 network
🔧 Major stability improvements across syncing, persistence, and connection handling

Whether you’re building collaborative editors, multiplayer apps, or real-time experiences, this update is all about getting you started faster with less friction.

Start building:
👉 https://t.co/pu0lv9Gp4K

Release notes:
📝 https://t.co/RBaZX2TEsg

Let me know what you’re building with it! 🙌
#realtime #crdt #webdev #startup #pluvio

[i3dly @i3dly_dev]

Been heads down the last 3 weeks building and shipping some major new features and improvements. Everything's finally ready 😎. Catch you guys this Tuesday with the latest 🫡

[i3dly @i3dly_dev]

I committed my Killing Floor game settings to GitHub. Why did I never think of doing that before? It's just a text file after all 🤔. Now I can just paste those settings whenever I get the random urge to play again.

[i3dly @i3dly_dev]

I'm finding the current wave of discourse around optimistic updates and realtime data syncing to be super interesting—yet a little strange 🤔. Tools like Supabase, ElephantSQL, Convex, and now TanStack DB are pouring serious engineering effort into solving this problem in a clean, typesafe way 💻.

Meanwhile, with libraries like Urql or Apollo Client, typesafety is first-class thanks to codegen 🛡️; optimistic updates have great DX because the frontend normalized cache automatically propagates object-type updates (with optimistic results replaced when mutations complete and return object-types); plus, GraphQL subscriptions make realtime syncing feel seamless 🔄.

That’s not to say GraphQL is without its many problems—I’ve actually been moving away from it more recently. But if you know early on that optimistic updates and realtime syncs will be essential to your app, it’s worth asking: will managing GraphQL be more or less painful than managing these concerns outside of GraphQL?

And if you require more specialized data-syncing solutions (like collaborative editing), look into CRDTs such as Yjs or Loro, and CRDT managers like https://t.co/h17BjQYMrD, which support strong eventual consistency of shared data 🔐.

#OptimisticUpdates #RealtimeSyncs #CRDTs #pluvio

[i3dly @i3dly_dev]

Welp. I definitely spoke too soon. https://t.co/VFsrz0whs4 works out of the box with slate.js. The others... will require some extra work. Guess I'm not ordering takeout tonight 🥲

[i3dly @i3dly_dev]

After yesterday's initial launch of https://t.co/h17BjQYMrD, I decided it's time to work on the next feature: rich text editor integration (e.g. slate: https://t.co/SVHpCGKnlH, lexical: https://t.co/fbWSbhe90S). And wow... I just followed the slate-yjs installation docs, and it... just works surprisingly 😯

If at the end of the day, I realize that I'm just shipping documentation, I'm ordering take-out 🥡

[i3dly @i3dly_dev]

imo, https://t.co/VFsrz0whs4 is the best way to build your realtime applications on @Cloudflare Workers. It's completely free to host on your own Durable Objects.

Come read the docs: https://t.co/jtnwA3eLOh
And check the launch on Product Hunt: https://t.co/0WWogWKXFs

[i3dly @i3dly_dev]

https://t.co/VFsrz0whs4 is now stable! If you ever wanted a realtime library with the DX of tRPC, come check it out!

Read the announcement here: https://t.co/mEmuiUEDOI
And find us on Product Hunt: https://t.co/0WWogWKXFs

[i3dly @i3dly_dev]

After having finished school almost 9 years ago, I'm finding it really hard getting back into writing 🥲. I guess when 90+% of the time your writing consists only of emails and slack messages, your ability to write longer-form content atrophies gradually.

Honestly much respect to those folks who write all of the technical content and documentation I consume on a daily basis as I now struggle to write my own 🫡

[i3dly @i3dly_dev]

Been building something behind the scenes for a while now 🧑‍🍳
Real-time. Collaborative. Built for developers ⚡
Almost ready to go. Dropping Monday 🚀 Stay close 👀