Be prepared. Anything can happen in software development.
Be prepared. Boy Scouts will recognize that motto. I’ve been reflecting on how much that short phrase shaped my career in tech.
Being prepared means more than just planning ahead; it’s about creating resilience.
- Establish regression testing so you can deploy with confidence.
- Verify backups before you need them.
- Predict strange user behavior before it surprises you.
- When something breaks, run a root cause analysis to make sure you’re better prepared next time.
Design systems? They’re preparation for the future.
Metrics? Preparation to explain what’s happening and justify decisions.
Documentation and processes? Preparation to help others succeed when you’re not around.
Monitoring and alerting? Preparation to catch issues before customers do.
Buffers in project plans? Preparation for the unknown.
Preparation is how you build trust, stability, and speed.
How do you prepare your team for the unexpected?
About the author
Brandon is an engineer who loves leading, planning, designing, growth and analytics.
Five books everyone should read:
Are Your Lights On, The First 90 Days, Elements of Persuasion, Humans vs Computers, When: The Scientific Secrets of Perfect Timing
Favorite quotes:
- Everybody has a plan until they get punched in the face.
- If a park ranger warns you about the bears, it ain’t cause he’s trying to keep all the bear hugs for himself.
- A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.