Bus factors & conspiracy theories (Friends)

巴士因素与阴谋论(老友记)

The Changelog: Software Development, Open Source

科技

2024-11-16

1 小时 18 分钟
PDF

单集简介 ...

Adam & Jerod discuss the news! Our Merch sale, useful built-in macOS CLI utilities, the slow death of the hyperlink, systematically estimating a project's bus factor, The Browser Company abandoning Arc, the Dead Internet theory & more!

单集文稿 ...

  • Welcome to Changelog and Friends, a weekly talk show about sweet, sweet merch.

  • Big thanks to our partners at Fly IO.

  • You know, we love Fly.

  • Finally, a public cloud that's built for developers who ship.

  • Check it out at Fly IO.

  • Okay, let's talk.

  • Hey, friends, I'm here with a friend of mine, Dave Rosenthal, CTO at Sentry.

  • So, Dave, I've heard you say Trace connected before.

  • I know that the next big frontier for Sentry is tracing this metrics platform, but how'd you get there?

  • And what do developers need to know about how you're thinking about this product?

  • Before I came to Sentry, Sentry was sort of working on a metrics product.

  • We started building that metrics product in, in a more traditional way with the metrics just kind of being more like kind of just disconnected.

  • They're just like another source of data.

  • They're another table somewhere.

  • Yeah, you can line them up by time, sure, you can drill into them a little bit, but really they weren't connected to that trace.

  • And we took a big step back from that after trying it ourselves, after trying it with users and realizing that there was a whole class of things we wanted to be able to do that you couldn't do with this kind of disconnected metrics.

  • And so, you know, we changed our APIs, we changed our approach, and we're kind of now really on a very clear direction of building a metric metric system that isn't one of these kind of like legacy disconnected metric systems.

  • It's trace connected so that we can get that kind of rich debugging context when you actually dig into a real problem and you know there's trade offs.

  • It's not quite as easy to just like log random metrics at random times into a system.

  • You have to put the thought when you're building the telemetry into how this metric actually does relate to the structure of the code that's running underneath.