Autosave gets tricky when the same field can be creating a record one moment and updating it the next. In Generations, quick edits on secondary parameters exposed that edge, so I collapsed create and update into one route and made the write path idempotent enough for rapid input.

An autosave feature is easy to pitch and easy to get wrong. The real work was making sure form writes survived unstable internet, page reloads, and rapid-fire input across a Rails app full of live data entry.