via: https://lobste.rs/s/m8uv5t/why_god_can_t_play_link_past

Web review of Ervin

Summary:

• Debugging is a mechanical process. You don’t need any great insight to debug your code, just patience and persistence.
• Although it’s mechanical, the challenge of debugging is at least partially emotional. You need to be comfortable with staying in a place where your code is broken and you’re not sure why, rather than just rushing to the quickest solution available.
• Debugging doesn’t just involve stepping through your code. It’s a process of stepping through your mental models.
• A bug almost always represents a place where your mental model diverges from the state of the real world.
• There are multiple kinds of mental model that you should maintain: at the level of lines of code, at the level of framework APIs, and at the (most difficult) level of the real-world problem your app is solving.

A lightweight Python utility that provides colored visualization of object attributes, making it easier to inspect objects during development and debugging.

Color-coded attribute display: 🔵 Blue: Dunder methods 🟡 Yellow: Protected attributes (starting with _) 🟢 Green: Public attributes and methods

We’ve all been here. Something works just fine on your computer but not on someone else’s. The root problem might be tricky, so I listed possible things you can investigate. Next time it happens, you have a list of things to check.

Great story about debugging a problem with a line-of-sight bridge that would only work when raining.

A long-form post outlining different techniques, tools, and mental frameworks for reverse engineering, using Facebook’s opaque Messenger API as the test subject.

On using JFR Analytics to locate a thread leak on a java application.