Most engineers spend their careers optimizing systems.
We obsess over:
latency
scalability
reliability
observability
But when it comes to our own daily habits, we accept systems with zero instrumentation.
Brushing teeth is a perfect example.
A system with no metrics
Imagine deploying a backend service where:
you don’t know which endpoints fail
you don’t know where latency spikes
you don’t know if users actually complete flows
That’s exactly how most people brush their teeth.
You perform an action twice a day, every day, for years —
and receive no structured feedback.
No missed areas.
No pressure data.
No consistency tracking.
From a systems perspective, this is… wild.
The missing layer: observability
What changed my thinking wasn’t a “smart feature”.
It was observability.
When brushing suddenly became observable:
I could see where I rushed
I could see how my behavior changed over time
I could correct errors without conscious effort
This mirrors what happens when you add logs and metrics to a service:
behavior improves simply because visibility exists.
No extra motivation required.
Why habits fail without feedback
We often blame discipline when habits break.
But in engineering, we know better:
systems fail when feedback loops are missing
users fail when signals are unclear
Daily habits are no different.
If you want consistency, you need:
clear signals
low friction
long-term reinforcement
That’s a system design problem — not a willpower problem.
Applying software thinking to physical behavior
Some newer consumer hardware quietly applies this logic:
turning physical actions into measurable data
showing progress longitudinally, not judgmentally
rewarding consistency instead of perfection
A smart toothbrush sounds trivial — until you realize it’s doing exactly what we do in production systems.
If you’re curious how observability thinking is being applied outside of software, here’s a concrete example:
👉 https://www.brusho.com
Not as a gadget — but as a system.
Top comments (0)