i only caught the last 10 min of @seebails awesome talk at @o11y2020, but he was on one of my favorite hobbyhorses: observability-driven development. 😍
When you're deciding what tech debt to address, don't go with your gut or lean on seniority -- *instrument* to gauge impact.
tech debt tends to bubble up to our awareness with unreliable cost indicators attached. but with o11y you can *instrument* -- who's using it, how are they using it, how much is it used, what impact would a fix have?
intuition is great, but measure before committing resources.
maybe the thing you thought was super important, the thing is super visible and offensive to you personally will turn out to be minimal, or maybe it will be a serious hit to users across the board. you don't know til you measure!
he quotes -- "if you don't learn to sell, you will always be working for someone who does know how to sell"
you've seen how people's eyes glaze over when you argue that it's time to do a painful library upgrade, or a complicated refactor, or to stop working on features and address db perf or cache strategy.
you need a shared denominator. and that is observability-backed SLOs.
You can follow @mipsytipsy.
Tip: mention @threader_app on a Twitter thread with the keyword “compile” to get a link to it.
Enjoy Threader? Sign up.
Since you’re here...
... we’re asking visitors like you to make a contribution to support this independent project. In these uncertain times, access to information is vital. Threader gets 1,000,000+ visits a month and our iOS Twitter client was featured as an App of the Day by Apple. Your financial support will help two developers to keep working on this app. Everyone’s contribution, big or small, is so valuable. Support Threader by becoming premium or by donating on PayPal. Thank you.