Measure what actually reaches the user
Engineering field guide · Coding and product value · Both days
Did the agent make delivery cheaper and the product better?
Connect code quality and product polish to delivery cost. Day 2 brings cost per merged pull request and accessibility requirements for coding agents.
All topic guides · Practical takeaways
Where the approaches meet
Section titled “Where the approaches meet”The talks connect generated code to the work of maintaining and using software. A passing build is one check in a larger delivery process.
How the approaches differ
Section titled “How the approaches differ”| Session | Approach |
|---|---|
| Capital One · Day 1 | Separates disposable programs from software that people will keep changing. Quality decisions depend on that expected lifetime. |
| Railway · Day 1 | Makes product behavior concrete: saving, undo, shared URL state, consistent patterns, and verification through actual use. |
| Jellyfish · Day 2 | Looks at the full cost of a merged pull request, including developer time and diminishing returns. |
| CAIS · Day 2 | Adds accessibility requirements before generation, including semantic HTML and keyboard operation. |
Capital One · Day 1 · Railway · Day 1 · Jellyfish · Day 2 · CAIS · Day 2
Where the evidence stops
Section titled “Where the evidence stops”CAIS’s reported 58% saving comes from one experiment. Railway’s “700 million tokens” aside is not a measured budget. Neither establishes an expected saving for your team.
Try this on your workload
Section titled “Try this on your workload”- Choose a small feature and write its acceptance, recovery, and keyboard requirements.
- Build it using the existing product patterns, then use it with a keyboard and test a failed save.
- Record total delivery time, including review and repairs, against a comparable completed feature.
Measure the result
Section titled “Measure the result”Track accepted functionality, accessibility failures, rework time, and full delivery cost. Keep code volume separate from the outcome users receive.
Read the source sessions
Section titled “Read the source sessions”- Capital One · Day 1. Our session notes · Official reading edition · Source video
- Railway · Day 1. Our session notes · Official reading edition · Source video
- Jellyfish · Day 2. Our session notes · Source video
- CAIS · Day 2. Our session notes · Source video
The comparison and experiment are our editorial synthesis. They are not a reported benchmark or the speakers’ prescribed procedure.