When the Baby App Crashed: Coding for Chaos (and Parenthood)
summary
An app that crashes at 3am prompts a rebuild in Python using Streamlit for quick UI and a write-first JSON persistence file so logs survive refreshes and offline use; feature control uses LaunchDarkly flags with per-user context-aware evaluation so charts, emojis and an external API can be toggled without redeploying; the UI stays separate from the durable write, the day view resets every 24 hours, the quick MVP ships in a day and a single survival mode toggle preserves core logging during incidents.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:18Baby app crash night
- 3:21Parenting and software development parallels
- 4:35Python and Streamlit choice
- 6:01Simple logging app design
- 7:16Data storage beyond session
- 9:18Feature risks and additions
- 10:31Feature flags beyond UI
- 12:27Handling API failures
- 13:38Survival mode with flags
- 15:28Context-aware flagging
- 16:34Future-proofing decisions
- 18:05Preparing for failure
- 18:59Conclusion and key takeaways
related talks
39mAdvanced Streamlit for Python Developers
27mCoding Competition Software VS Murphy's Law
32mBuild a data visualization app for your phone
49mUntitled13.ipynb
26mYour app is async so take advantage of it for development!
29mGive Apps Online Superpowers by Optimizing them for Offline
01h 08m"Lightning Talks"
13mMobile Education App during COVID