Unintended consequences of well-meaning changes
summary
A secure-but-overzealous IP whitelist spawns a chain of proxies so long developers bypass testing and push emergency patches that leak customer data; creating empty unit-test projects wipes the visual signal that tests are missing and momentum dies; a rigid content tool blocks legitimate workflows and prompts DB admins to run risky queries that accidentally publish embargoed content. Practical fixes: zoom out and ask “and then what”, map feedback loops, couple unit-test checks to code reviews, and design a pit of success so the easy path produces the desired behavior.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:35Locking test environment
- 9:56Monolith testing push
- 15:39Feedback loops in systems
- 21:59Rigid internal tool effects
- 34:27Summary
related talks
26mTake a step back
40mHow to fail a software project fast and efficiently?
16mPaved roads to hell: Antipatterns of platform engineering efforts
28mWith great power comes great responsibility
32mMaking Sotware Better, Despite Having Users
32mStop Automating, Start Investigating: Slow Down 2 Speed Up
50mFix The Damned Software
37mFear Driven Development