Let's talk about the observability course. One of the interesting questions that has come up is "Why not do this with vendor "
In my career, I've used both open source and vendor supplied tooling to view application telemetry. On balance ... they're both fine. They make very different tradeoffs — open source can have horrifyingly high staff costs, versus vendors which can (ironically) be very opaque. From an engineers perspective though, it doesn't matter so much.
What matters is how well you can reason through your system. The problem you're looking to solve is "Why is my Go application slow", and not "How do I make this graph pretty". The course uses open source tooling so you understand steps to get data from Go in a UI, but the focus is rather on "How can I see the garbage collection state of Go in Data" to help answer "Why is my application slow".
Want to learn more? Check it out at h4n.link/pito.
Custom
Can think about a new callout for h4n.link which is at the bottom of the screen. Prefix that callout with the link character (🔗)
What should the content of the short?
Let's talk about the observability course. One of the interesting questions that has come up is "Why not do this with vendor"
In my career, I've used both open source and vendor supplied tooling to view application telemetry. On balance ... they're both fine. They make very different tradeoffs — open source can have horrifyingly high staff costs, versus vendors which can (ironically) be very opaque. From an engineers perspective though, it doesn't matter so much.
What matters is how well you can reason through your system. The problem you're looking to solve is "Why is my Go application slow", and not "How do I make this graph pretty". The course uses open source tooling so you understand steps to get data from Go in a UI, but the focus is rather on "How can I see the garbage collection state of Go in Data" to help answer "Why is my application slow".
Want to learn more? Check it out at h4n.link/pito.
Custom
Can think about a new callout for h4n.link which is at the bottom of the screen. Prefix that callout with the link character (🔗)