Using data to make decisions is actually really hard. Yet nearly every tech company, business, and team touts “data-driven” as the de-facto way that they operate. In practice, this intention to be data-led is often just aspirational—only about a quarter of organizations report that they are actually data-driven, according to Harvard Business Review. It’s easy to see why organizations strive to more effectively use their data.
When Plastic SCM (now Unity Version Control) was acquired by Unity in 2020, game dev and VFX studios already using the Unity Engine started considering it more seriously for version control. Why? On the surface, Plastic SCM is an attractive solution. It offers a friendly UI for artists and handles the basics of version control at low scale. But what happens when your projects grow and get more complex? Does Plastic still hold up? Read along or jump ahead to the section that interests you most.
This article will teach you how to monitor Ruby errors without using a service like Honeybadger! Learn about Ruby's built-in errors, how to use log levels and tagging to customize the log output, display errors on the front-end, and more.
Logs are essential to any application's development. Most Ruby logs are verbose and chunky, so digging for exactly what you need can be difficult. Even though they contain useful information, you might not get as much value as you should from logs if you don't know how to use them effectively. In this article, we'll explore: Let's get started.
Node.js 12.x onwards introduced async stack traces. Async stack traces allow developers to view the call stack of asynchronous code, making it easier to trace and debug code issues. In this post, we’ll see how async stack traces work, how you can use them to debug code, and how to track them using AppSignal. Ready? Let's get going!
