はてなブックマーク

This is the final post in a series on how we scaled Bugsnag’s new Releases dashboard backend pipeline using gRPC. Read our first blog on why we selected gRPC for our microservices architecture, and our second blog on how we package generated code from protobufs into libraries to easily update our services. The Bugsnag engineering team recently worked on massively scaling our backend data-processin

At Bugsnag, we recently launched the Releases dashboard for tracking the health of releases. It was a large undertaking, but as we built out the backend to support it we paid particular attention to performance. One of the key areas we focused on was the latency associated with our backend service calls and, in the end, we chose to switch out REST for Google’s blisteringly fast gRPC framework. In

Have you ever wondered what happens to your Android application code when it’s compiled and packaged into an APK? This post takes a deep dive into the Dalvik Executable Format, with a practical example of the structure of a minimal Dex file. What is a Dex file? A Dex file contains code which is ultimately executed by the Android Runtime. Every APK has a single classes.dex file, which references an

There are numerous benefits of using tmux. The benefits I discussed there are independent of one’s choice of text editor. But if you’re a vim user, the benefits of tmux reach even further. One of the best aspects of tmux is that it unlocks the potential for a more powerful vim-based development environment, allowing vim and the shell to feel more like a single cohesive tool. In this post we’ll loo

One of the ongoing initiatives for the Bugsnag Frontend Team has been a migration of our codebase away from coffeescript. It hasn’t been an easy journey, and it isn’t yet complete, but we thought we’d share what we have learned from this process and how we have managed to speed our conversion without overly sacrificing productivity or stability. Why move away from coffeescript Javascript has becom

PLATFORM Error monitoring & reporting for Rails apps Automatically detect Ruby on Rails exceptions, prioritize what needs attention, and find the answers you need to quickly resolve errors and ship applications with confidence.

A few months ago, a number of designers and UI engineers, inspired by a popular blog post from GitHub’s Mark Otto, published articles on their approaches to writing and organizing CSS. In this post, I’m going to follow suit and take you through a breakdown of the tools we use, as well as the architecture of BugSnag’s CSS. There’s no surefire method for organizing CSS for all situations; the conten

PLATFORM Error and performance monitoring insights for JavaScript applications Automatically detect JavaScript errors on your website and optimize website performance by monitoring real user experiences in real time. Real time browser performance insights Real user monitoring insights into web performance to rapidly identify lags and get the context you need to fix the root cause. Leverage user me

GitHub recently released the awesome Atom text editor, and although many of the keyboard shortcuts will be familiar to Sublime Text users, there are many subtle differences. Here’s a quick cheat-sheet for the keyboard shortcuts Atom provides, to help you become a keyboard master. If you’d prefer this in downloadable form here’s a single-page printable version to keep on your desk: We also have a c

Bugsnag has been using pry as a replacement for ruby’s irb console since before I joined (disclaimer: I’m one of the pry core team). It’s better than irb for a number of reasons, but chief among them are that it syntax highlights input and output, and it crashes less often. This is most useful in development, when you spend a considerable amount of time in the console, but it’s also useful in prod

Error monitoring in JavaScript is a thorny problem. On the one hand window.onerror will at least notify you when something goes wrong. On the other, it won’t give you enough information to actually debug the problem. Notably absent in many cases is the stack trace. That said, with a little bit of work it’s possible to get stacktraces that are reasonably complete in all browsers. Bugsnag’s JavaScri

Blog Introducing BugSnag Real User Monitoring for Flutter & React Native Applications

Blog Introducing BugSnag Real User Monitoring for Flutter & React Native Applications