Debugging

Every web developer uses Chrome DevTools. We inspect elements, read console logs, watch network requests, throttle CPU, emulate mobile screens, record performance traces, check storage, debug JavaScript, and capture screenshots. Most of that feels like a browser UI. Under the hood, there is a protocol. That protocol is Chrome DevTools Protocol, usually shortened to CDP. CDP is the browser debugging API that lets tools instrument, inspect, debug, and profile Chrome, Chromium, and other Blink-based browsers. Chrome DevTools itself uses this protocol. Many automation and debugging tools also build on it directly or indirectly. ...

Most developers only think about source maps when DevTools magically shows the original TypeScript instead of unreadable bundled JavaScript. That convenience hides an important fact: A source map is not just “debug metadata.” It is a translation table between generated code and original source code. And depending on how it is emitted, it can contain the original source itself. That is why source maps sit at the intersection of: debugging build tooling browser DevTools error reporting systems like Sentry security and accidental code exposure If you have ever wondered how a minified file can still produce readable stack traces, or how a published .map file can expose a package’s real TypeScript source, this is the mental model you want. ...

When people say they want to “search in CloudWatch”, what they usually need is CloudWatch Logs Insights. It is much more useful than manually opening individual log streams because you can search across log groups, combine conditions, sort by timestamp, and limit results quickly. That said, AWS also has the basic log search interface inside a log group. If you select all streams and search there, the syntax is different. It uses filter patterns, not Logs Insights query language. ...

Introduction If you’ve ever stared at a cryptic error message from a CLI tool wondering “What HTTP requests is this thing actually making?”, you’re not alone. Whether it’s a failed git clone, a mysterious npm install error, or tracking claude code for finding prompts, finding out what data your application sends to third-party services, understanding HTTP traffic is crucial for modern development. Enter HTTP Toolkit – an open-source powerhouse that makes intercepting and debugging HTTP traffic almost effortless. ...

Introduction Complex tasks, such as writing unit tests, can benefit from multi-step prompts. In contrast to a single prompt, a multi-step prompt generates text from GPT and then feeds that output text back into subsequent prompts. This can help in cases where you want GPT to reason things out before answering, or brainstorm a plan before executing it. Multi-Step Prompting Technique We will use a 3-step prompt to write unit tests in Java ...

jps (Java Process Status) Usage: Sample Usage: Understanding the Output: jstat (JVM Statistics Monitoring Tool) Usage: Sample Usage: Understanding the Output: jcmd (JVM Diagnostic Command) Usage: Sample Usage: Understanding the Output: jmap (Memory Map for Java) Usage: Sample Usage: Understanding the Output: Conclusion Java applications often run in complex and dynamic environments, making it essential to monitor their performance and diagnose issues efficiently. Fortunately, the Java Development Kit (JDK) comes with a set of powerful tools for this purpose. In this guide, we will explore four essential tools: jps, jstat, jcmd, and jmap. We’ll discuss their functionalities, sample usage, and how to interpret their output effectively. ...