If you’re a developer, you need a personal website. While billionaire-owned, algorithm-based social media platforms arbitrarily decide what people should and should not see on their timelines, there’s no better time for you to carve out your own cozy corner on the web and own your content.

To the Sentry community - It was sixteen years ago that David Cramer pushed the first commit to a side project, and twelve years ago when he and Chris Jennings turned this side project into a company that exists to solve a simple problem: making debugging any software issue dead simple. Since then, we’ve been on a path slightly different from what most people consider “observability.” Sentry isn’t a platform or a company that wants to collect logs and check a monitoring box.

Sentry is pretty good at capturing all your production issues. But sometimes your user hits an issue that doesn’t fire an exception – maybe a broken link, problem with their permissions, or even something as simple as a grammatical error in copy. Sentry won’t capture those, but you should probably know about them so you can fix them.

If you know me, you know I care about fast code. Recently, I ran a simple query that revealed that we spend almost $160k a year on one task. Luckily, we launched the Metrics beta back in March. Over the last month or so, 10 of us Sentry engineers collaborated across many functions to leverage Metrics to track custom data points and pinpoint the issue leading to this ridiculous ingestion cost.

Minifying your CSS helps improve your website performance. But as developers, we don’t really talk about minifying CSS anymore. Why? The TL;DR is that the delivery and optimization of CSS have both been improved with modern tech stacks, making it practically a non-issue. The efficient and performant delivery of CSS is largely solved by HTTP/2 and modern compression algorithms, whilst modern front end frameworks take care of the boring optimization jobs such as code-splitting and minification.