Why I Expose Incidents on a Personal Site
•1 min read
opsobservabilitypersonal-brand
Reliability is part of the portfolio
If I claim I care about engineering quality, availability should be visible. A status page makes that claim measurable.
What I track
- Service health summaries
- Incident timelines
- Basic system metrics
Why this matters
A static portfolio often hides operational thinking. By showing uptime and incidents, I can discuss tradeoffs around monitoring, rollback strategy, and blast radius during interviews.
Cost and complexity
I intentionally kept the dashboard lightweight and static-friendly. The key is signaling engineering intent without introducing unnecessary operational burden.
In short, transparency builds trust faster than polished screenshots.