At Rollbar, we care about reducing the time it takes developers to find and fix errors. This is why we’re making our integration with GitHub even stronger to provide more context around errors and reduce the mean time it takes to resolve them MTTR. Last year, we launched Code Context to show additional lines of code within each frame of the stack trace, reducing the back and forth between GitHub and Rollbar.

Well, my developer friends, 2020 is your year. Businesses in practically every industry have a fever to grow their IT operations and automate just anything possible. I know, I know. The demand for developers is nothing new. But 2020 is different. 2020 is the year where we see some of this decade’s most exciting technologies become commercially viable, and others finally go mainstream.

We are introducing a new version management process for our steps from Week 9, 2020: you'll be able to lock for major and minor versions instead of the old always latest and specific versions.

In the first post of this series, we looked at the state of your organization, how to tell if Microservices are right for you, and wrapped up with a few challenges this architecture brings to the table. In this article, we will look at organizational changes that will help you adopt a Microservice architecture. Additionally, we will touch on topics like how to bring change to your organization, how to embrace the primacy effect, and why you should embrace cross-functional teams.

Breadcrumbs can help you debug client-side JavaScript applications, and are available to all Honeybadger customers as of today. One of the things that makes fixing JavaScript errors so difficult is that everything happens on the client-side. When an obscure error happens in a callback, you often lack the context to reproduce it. If the error is critical, you may even resort to deploying debug code to get more information about the events leading up to it.

Learn to write real-world Unit/UI test cases for your iOS app in this practical testing 101 article for absolute beginners, written by Tibor Bödecs (The.Swift.Dev).

RoR (Ruby on Rails) is a server-side web application framework. To make it more secure, use HTTPS instead of HTTP.

It’s Friday afternoon, the majority of the development staff has already packed up and headed home for the weekend, but you remain to see the latest hotfix through to production. To your dismay, immediately after deployment, queues start backing up and you begin to get alerts from your monitoring system. Something has been broken and all evidence points to an application performance bottleneck.

Logging is an essential part of just about any PHP-based application; whether in a script or a larger application. However, how little is too little and how much is too much to log? If we don't log enough information, when something goes wrong, as it invariably does, then we won't have enough information available to determine what went wrong so that we can fix the problem. However, if we have too much information, then we'll be unable to filter out the white noise.

You know Big-O is important - not only for acing your next job interview but for knowing how code works at scale. But have you ever taken the time to go beyond a superficial understanding of the subject? In this article, Julie Kent uses equal parts math and Ruby to reveal the beating heart of Big-O and show us how it ticks.