This guide provides instructions for setting up an environment for developing, debugging, and programming embedded systems firmware in the Windows Subsystem for Linux (WSL2). WSL2 provides a convenient and stable Linux development environment for working on embedded systems firmware. If you’re curious about toolchain performance, check out this comparison of firmware development environments, but the summary is that WSL2 is about 2x the speed of Windows and similar to “bare metal” Linux.

Snuba, the primary storage and query service for event data that powers Sentry in production, has historically been doing rate limiting under the hood, making it hard to discover and increasing time to resolve customer support requests. This is not something you’d know the specifics of unless you were deep in the Snuba code. But as we triage support questions from customers, one issue tends to pop up: RateLimitExceeded. You got tired of not getting query results.

Sentry is committed to helping developers fix broken code quickly and effectively. In this article, we’ll cover a range of intermediate to advanced techniques for debugging Python code using VS Code and the Sentry Python SDK.

Debugging. It’s a critical skill for all developers. And when you’re building a dynamic, high-performance application with Next.js, Chrome DevTools, and console.log() aren’t always enough. There are more effective and structured ways to debug Next.js apps as they scale. You will also find practical tips from our Next.js debugging workshop sprinkled throughout. Also, while this guide is focused primarily on Next.js, there is a similar guide for debugging React apps here.

At Ultrahuman, innovation is at the core of everything we do. Our health devices, powered by the nRF52840 SoC for BLE functionality, rely on Nordic Semiconductor’s renowned wireless technology. For years, the nRF5 SDK was the cornerstone of firmware development for these chipsets, but in 2018, Nordic introduced the nRF-Connect SDK(NCS), built on Zephyr RTOS, signaling a new era for BLE applications.

As developers, we know that debugging can be a time-consuming process. Hunting down elusive bugs or trying to reproduce an issue based on vague user reports can turn a simple fix into an hours-long journey. While leveraging logs, metrics, and tracing to reproduce locally or try to understand what happened can help us identify a root case, we’re often missing a critical component to truly being able to understand the impact on our users.

Learn how to use the Grok Debugger effectively for log parsing, with practical tips, debugging techniques, and pattern optimization.