Your Bug Report Can Fix Itself by Morning
A system named Sandy sifts complaints from the product, support, and X, and saves human judgment for what users actually see.

Y Combinator · The Rise Of AI CoworkersAt 3 in the morning, small software bugs are getting fixed and shipped. The overnight worker is Sandy, an automated system that scans thousands of customer comments daily.
The complaints arrive from three places: reports sent through the product itself, support channels, and posts on X. A lot of that feedback is just small bugs.
For those small bugs, Sandy writes the fix, merges it into the code, and sends it out automatically. Built by engineer Lauren Tan as part of her software factory, it often ships without anyone thinking about it.
Tan keeps this self-healing work separate from decisions that need human judgment. For her own factories, she does not turn them toward feature development, aiming them instead at maintenance, such as performance, bugs, and quality of life complaints.
Anything that changes the details users see and touch every day gets slower treatment. A button that moves one morning and moves again the next is frustrating, so the team tests such changes by using them internally first.
They live with a visible change longer than feels comfortable before releasing it. If it does not win over people inside the company, or gets a mixed reaction, it does not ship.
Work that once occupied a full-time person now runs in the background, freeing engineers to think more deeply about the product experience and what good design requires.
Questions people ask
What does dogfooding mean?
Dogfooding means a team uses its own product the way a customer would, before outsiders see a change. It catches annoyances that look fine in code but feel wrong in daily use, like a button in an awkward spot.
Why start with small bugs instead of big features?
Small, isolated bugs are a good fit because the cause and the fix are usually clear. Larger features involve tradeoffs about what the product should do, which requires goals, context, and taste that are harder to automate.
Why ship software at 3 a.m.?
Overnight releases affect fewer active users, so there is less disruption if something needs a quick correction. Teams also commonly run automated tests before release, and can roll back a change in the morning.
