What’s actually inside the thing everyone else just uses?
Day to day I lead engineering enablement across HoneyBook, which lately means working out how a whole org builds with AI agents without making a mess of it.
Six packages I maintain get about 3.1 million downloads a month. The first one went out in Feb 2018.
I’ve given five conference talks since 2022, in the US, Europe and Israel.
When you build an agentthat actson a user’s behalf, letting the agent decide whether to ask first leaves the userto chance. This article works out where that decisionshould live.
Bob’s HACK button freezes the pagefor a second,and the fix he finds is the oldsetTimeout(…, 0) trick. This post follows his click through the event loop to seewhat that trickreally changes.
Your field data can look perfectly fine while the score sits at 70. Most people reading that number decide the siteis slow,so the score ends up mattering because it matters to them.
A function signature grows until the callsite readsgreet('John', undefined, false, undefined, 'Mr.'). Nothing stops an agent adding a sixth argument, and whoever reads that line later pays for it.
A builderis a functionthat gets validated options and a context,and reports back whether it worked. Everything around it —the package entry,builders.json,the schema —is how Architectfinds it.
I fix the list’s keys, re-record,and the numbers are identical — same renders, same duration. What movedis the reasonthe Profiler gives for each render, and that reasonis what tells you which fix to try next.
Custom hooks reuse stateful logic and isolate it at the same time. Moving the calculationbehind a context provider is what gives you control over how often it runs, and wherein the tree.
An extensionis several separate execution contexts that happento shipin one folder, and Angular only ever lives in oneof them. Most of the friction comes from a buildthat doesn’t know that yet.