Logs, Tears and Feature Flags: Code Stories in Survival Mode
summary
A Python app rewrite using Streamlit stores critical sleep-and-feeding records in a local JSON store instead of Streamlit session state so data survives crashes and different devices. Nonessential charts and emojis are gated by LaunchDarkly feature flags, and a runtime "survival kill switch" context disables optional features and an unreliable external API without redeploy. The setup preserves offline critical data while letting experiments be toggled live so the app remains usable at 3 a.m.
AI-written summary · about
chapters (9)
- 0:00Tech failure night
- 1:55Dev to mom
- 3:39Python app with Streamlit
- 5:58Architectural error
- 7:22Adding charts and emojis
- 9:12External dependency risks
- 11:23Feature flags saved production
- 13:28UI, data and recovery
- 14:10Maternity and dev lessons
related talks
29mSelf-Destructing Feature Flags
54mFeature Flags Separate Deployment from Feature Release
42mStreamlit: A Faster Way to Build and Share Data Apps
28mBeyond Prototyping: Building Production-Level Apps with Streamlit
01h 58mHow to create beautiful interactive GUIs and web apps
01h 09mTurn Python Scripts into Beautiful ML Tools
15mFeature Flags
18mStreamlit: The Fastest Way to build Data Apps
