His ticket-driven agents mock up, build and verify each change before he sees it
Ticket-driven agent setup: he adds a ticket, it makes a mockup and writeup, he approves, and it spins up a temporary webserver and iOS and Android builds to verify; review and testing loops run automatically.
How it works
- He adds a ticket
- The setup makes a mockup and writeup
- He approves
- It spins up a temporary webserver and phone builds to verify the change
Why it’s worth knowing
The approval sits exactly where the cost of a mistake jumps.
Where it’s from
Summarized from a public post on news.ycombinator.com. See the original ↗