Resilient Code, Resilient Engineer: Lessons from Changing Requirements
summary
A four-step Elixir LiveView form with separate live components and embedded Ecto schemas becomes resilient: moving shared form state into the LiveView parent state stops repeated API calls and preserves validation errors, keeping each component as a live component for complex UI and events. The team deletes the review step, replaces it with a simpler parcel scanner, and the result reduces API traffic, simplifies schemas, and survives several shifting requirements without rewriting the whole UI.
AI-written summary · about
related talks
01h 01mArchitecture Decisions: A Case Study -
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
47mGood behaviour: Cultivating Healthy Elixir Teams & Codebases
39mKeeping Code Consistent
40mKeynote: The Pendulum
59mKeynote: Elixir Should Take Over the World
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance