Want to build landing pages in the command line whilst keeping marketing happy? https://t.co/qyfmisSKMX

Her: take me to somewhere expensive Me:

Cloud costs are getting out of control. Most leaders I talk to have seen the unexpected invoice at the end of the month. I'm building an app to allow your team to track costs on infrastructure. Check it out:

Loving the presentation from @euruko by Victor with things he's learned after 25 years. Loving the "birds aren't real" reference!

🚀 It’s Day 1 of #EuRuKo2024! Three days of inspiring talks, workshops, and connecting with the Ruby community are officially underway here in Sarajevo. Let’s make this an event to remember! #Ruby #TechConference #TechTalk

At #EuRuKo2024 - super cool conference! I'm here and wearing a red T Shirt with "Fix Bugs 20x Faster" on it. Come and say hi and ask me what goat I have!

9:18am - "Test suite is really slow, wonder why." 9:58am - "CI tool only gives basic metrics. Sigh." 10:12am - "Let's add structured logging." 2:49pm - "First test run! Let's see..." 2:52pm - "73% of the time is from 18% of the tests... WTF?!"

Ruby Warsaw Community Conference is over. Thank you to all the speakers, sponsors, and everyone involved in this event. It was a good day.👌 See you in February for the next edition!💪 #rubyonrails #conference

Just listening to @noahkagan 's amazing Million Dollar Weekend. I've just asked for 10% off on my evening meal... in a random hotel in Warsaw... feeling very foolish... and get rejected. YASSS. I'm not new to rejection challenges but this is awesome.

This little calculator app allows you to explore the effect of sampling to the accuracy of: 1. Request Rates 2. Error Rates 3. Latency Percentiles You may want to use this, if you are sampling your tracing data. @LightstepHQ @ZalandoTech https://t.co/hAGwJ4v7Zd

Using this approach at BiggerPockets we went from an impenetrable black box to understanding how our app was actually being used. The goal? To make software engineering *joyful*. ✍️ DM me MORE ♻️ Repost if you think this is useful

✅ 5. Improve Maybe the data didn't show up. Maybe the data did show, but you now realise you'd made a mistake. Maybe you got your question answered and now you have another question. Or improve the instrumentation. Or choose a new question!

✅ 4. Use Create facets and indexes for your new data if needed. Query your observability tool for the data you wanted to collect. Big reveal - was your question answered?

✅ 3. Build Instrument your app to gather the data you need. This might be tweaking the current instrumentation. Deploy it.

✅ 2. Decide Decide which data you need. "I need to know the latency for our mailers." "I need to know the retry count and the current retry number of every job." "I need to know the controller, action and duration of every request."

✅ 1. Question Think of a question you'd love to answer: "Why did Michelle not get her landing page link via email?" "How often are jobs going to the dead queue?" "What are the slowest endpoints in our app?"

Ever been overwhelmed by observability? "I don't know where to start!" Here's how I've successfully instrumented real apps, step by step.

The Three Pillars of observability are nonsense. They're actually three data types. Let's tear down the silos. #kill3pill

The @o11ycast crew and @mipsytipsy have been integral in my transition from DevOps to observability. We need to see what our code and systems are doing from the moment they are deployed, not just when they break: instant feedback. Observability is a mindset, not a tool set.

Observability - the new focus for my newsletter.