Jimmy Moon (현경, 炫炅) 👨‍🔬

Why is Vercel CI faster than just "faster CPUs"? Caching, shared dependency installs, maximum concurrency. 1. Task caching by default Tasks only run if they could have been impacted by the current diff. And it isn't like the task boots and then terminates because there is nothing to do: The task never even starts because the orchestrator is aware of the caching. This saves wall-clock time and $$$. 2. It installs dependencies once and then shares them between all tasks 🤯 Have you ever babysat a CI job 30 minutes in and wondered why it is running `pnpm install` again? Vercel CI never does that. This saves wall-clock time and $$$ 3. It runs all tasks at maximum concurrency. In legacy CI systems you can manually configure task fan-out, but that is tedious and often bit rots. Vercel CI always runs tasks as soon as possible and all tasks that can be concurrent get their own VM and run in parallel. Increasing concurrency is cost-neutral while massively reducing wall-clock time. vercel.com/blog/introducing-…

Cursor's new Agent SDK follows @eve's conventions in many cases to the letter. I think that is amazing. A new standard for agentic development is emerging similar to how file-base routing became a thing across many web frameworks. eve.dev/docs/tools cursor.com/docs/agent-sdk/qu…