MCPs, Skills and CLIs
A teammate asked if Skills replace MCP. They don't, and the CLI half of that argument turned out to be the interesting part.
Software Engineer at Netlify. I work at the seam where product, design and engineering stop being separate jobs.
A teammate asked if Skills replace MCP. They don't, and the CLI half of that argument turned out to be the interesting part.
What you get when you rebuild TCP's reliability on top of UDP in user space, and drop the parts that hurt.
Every HTTP version exists to fix the bottleneck the last one created. The whole arc, briefly.
TCP is a reliable byte stream, UDP is fire-and-forget messages. The short version, with Node socket examples.
We build tools to stay beneath us and children to surpass us. AI is the first thing we have made that sits between the two, and we have not picked a word for it yet.
Monads in plain JavaScript: Maybe, map, chain, Promise, and why the weird box thing turns out to be useful.
Signals, effects, and computed values built from scratch in plain JavaScript
LRU, LFU, TTL, write-through, write-back, and cache stampedes explained with interactive demos
The scope chain drawn out, then closures at work as private counters and run-once functions, with the var loop and memory traps.
Array.prototype.sort explained, custom comparators, and stability quirks
Map, forEach, filter, reduce explained from scratch
Pure functions, immutability, higher-order helpers, reduce and composition, ending in a small project that uses all of them.