Dense Operational UI with Tables and Editors
Why some product workflows need dense tables, dirty-state tracking, and careful batch saves.
Read storyWhy some product workflows need dense tables, dirty-state tracking, and careful batch saves.
Read storyWhy AI tools need schemas, permissions, confirmation, and audit trails before they change product data.
Read storyHow I split workflow tests between fast service checks and a few browser paths that matter.
Read storyHow runtime validation and readable docs help keep public API behavior from drifting.
Read storyWhy I used a database-backed job queue for slow product workflows, and what had to be visible to users.
Read storyWhy durable product state belongs in the database, and where Prisma should stop leaking into the app.
Read story