iiinova — where your digital self keeps evolving

Subscribe to Neciu Dan's Newsletter

Want the next edition in your inbox? One email a week with my new articles, Señors @ Scale episodes, and the best reads I find. Plus memes, book recs, and conference discounts. neciudan.dev/subscribe

neciudan.dev

Get the latest articles, insights, and exclusive content delivered straight to your inbox.

000

A Simple Guide to Calm UI

Max Schmitt argues against toasts, since they pop up far from your click and vanish before you notice. He keeps the spinner on the save button until the list refetches, so the UI changes only once. Try both demos. maxschmitt.me/posts/calm

maxschmitt.me

220

the senior engineer death spiral

Starting a senior role? This is a must-read this week. Sunil Pai wrote such a beautiful article that resonated with me deeply. His line that software sits downstream of your reputation makes so much sense. sunilpai.dev/posts/the-se...

sunilpai.dev

on proving yourself, burning out, and being a good teammate

100

Inside Chats: How Lovable's Agents Work Together | Lovable

Lovable keeps each agent conversation as an append-only log, one parent per event, like Git. I like how Agents write to each other's inboxes and send a wake-up, letting runs survive deploys. From Rouzbeh Delavari lovable.dev/blog/how-lov...

lovable.dev

How Lovable's agents work together through trajectories, inboxes, and activations—the Git-inspired event log and Agent Control Plane behind Chats, streaming, forking, and agents that survive deploys.

100

Rapidly scaling online storage to serve over 1 billion ChatGPT users

OpenAI kept Habitat in Python up to 20M requests per second and bet Codex would make the rewrite cheap later. Two engineers moved it to Rust in one quarter. openai.com/index/scalin...

openai.com

Learn how OpenAI evolved Habitat from a Python library into a globally distributed storage platform serving 1 billion ChatGPT users and 22M requests per second.

100

How we built Git storage for millions of Netlify projects

@netlify.com found that 93% of new projects have no Git host, so they rebuilt Git piece by piece to handle it. Now every project gets a real Git repo on S3, and clean agent merges take a second and zero tokens. From Philippe Serhal www.netlify.com/blog/how-we-...

netlify.com

A technical look at how Netlify built Netlify Source: durable Git storage on S3, scalable caching, push consistency, and support for millions of projects.

100

Subscribe to Neciu Dan's Newsletter

Edition 30 of my newsletter is out 📬 Five community reads this week. My take on each one below 🧵 neciudan.dev/subscribe

neciudan.dev

Get the latest articles, insights, and exclusive content delivered straight to your inbox.

120

Neciu Dan @neciudan.dev · 25/09/2026

It covers more the components side

000

What a Design System Is Really For with Szymon Chudy @chudy.me (5’ video) If you enjoy this please Like and Subscribe (It helps) 🔥 🔥🔥 youtu.be/5n9NWu4xDGc

youtu.be

What a Design System Is Really For with a Netflix Engineer

YouTube video by Neciu Dan - The Señor Developer

110

Neciu Dan @neciudan.dev · 24/09/2026

And Spotify 🎧 open.spotify.com/episode/2R4p...

010

Neciu Dan @neciudan.dev · 24/09/2026

Dont skip this episode with @chudy.me Pure gold youtu.be/O1tzjZKzPpk

142

Neciu Dan @neciudan.dev · 23/09/2026

@chudy.me on the latest Señors at Scale episode Full episode link: youtu.be/O1tzjZKzPpk

161

Neciu Dan @neciudan.dev · 21/09/2026

💬 "Design systems are slower than product. People are usually angry about that, but I think it's a feature, not a bug."- @chudy.me Listen now 👇 ▶️ YouTube: youtu.be/O1tzjZKzPpk 🎧 Spotify: open.spotify.com/episode/2R4pAOIYVX…

000

The library for web and native user interfaces

3️⃣ use(browser()) Every SSR app has that one component that needs localStorage or the local time zone use(browser()) suspends on the server and does nothing on the client. The nearest Suspense fallback goes into the HTML, and the component renders normally after hydration. react.dev/blog/2026/09...

react.dev

React 19.3 – React

100

2️⃣ Fragment refs If a component renders a list of siblings with no parent, or comes from a library that doesn't forward its ref, getting to its DOM nodes meant adding a wrapper div that messed with your layout Now you pass a ref straight to <Fragment> and get a FragmentInstance with addEventListener

100

1️⃣ <ViewTransition> Until now, animating a component entering, leaving, or moving meant an experimental build or building on top of the browser's View Transition API yourself. Now you wrap the part of the UI you care about, and any update inside startTransition gets animated.

100

⚛️ React 19.3 is out I've written about this before, but now it's official. Let's see what we get 👇

100

3️⃣ z.withParser() — z.compile() builds its fast parser with new Function, which a strict Content Security Policy blocks So the fastest path in Zod was off limits in the apps that care most about security. withParser() lets you generate the parser at build time and plug it in under the same contract.

120

2️⃣ z.instanceof().properties() — If you try to validate a fetch Response with z.object(), you get back a plain object, and the prototype is gone, and so is .json(). Now you can validate properties on a class instance in place and get the same instance back with its methods intact.

110

1️⃣ .validate() — Until now, asking "is this input valid?" meant calling safeParse, which walks the whole input and builds a ZodError with an issue object for every failure .validate() returns a boolean, aborts on the first error it meets, creates no issue objects at all, and narrows the type

110

💎 Zod is my favorite library (after React Query) Version 4.6 is out 👇 Here is what I am excited about in the update from @colinhacks.com

190

New Episode is live!! Agentic Systems at Scale with Vilva Athiban (Omio) | MCP, Orchestration Agents&LLM Cost Optimizatio Full episode is here 👇 youtu.be/WXtrBMlJjQo

000

4️⃣ They now design v0 for 10 to 20x the load they can see. Agents open smaller PRs, push overnight and on weekends, and PR approval keeps getting faster, so CI job volume grows exponentially rather than with headcount. Is this the future?

100

3️⃣ They pointed a long-running Claude Tag session at the service's metrics. Whenever the listener fell more than 50,000 jobs behind, it pinged the engineer with the full context of previous fixes, and after the rewrite, it tuned journal size and worker count on its own.

100

2️⃣ The service used to keep all test history in the memory of one process, so it could never be sharded. Now every CI result gets appended to a journal in an in-memory store. A consumer rolls that journal into per-test history every few seconds, and the selector reads from there.

100