• 0 Posts
  • 171 Comments
Joined 2 months ago
cake
Cake day: August 7th, 2025

help-circle




  • I recently looked into this on another forum where someone shared some articles supposedly proving bias. One article was itself highly biased to the right, so not particularly credible.

    The other article, from an organization that ranked the bias of news sources, was very neutral and objective, took accusations of bias seriously, went into detail, and removed the “unbiased” classification from Wikipedia, but didn’t conclude any provable bias, leaving it unranked. The best example of bias they had was the fact that articles on socialism and communism didn’t list Soviet atrocities, but those atrocities have their own pages and are also mentioned on pages of the countries involved, so that was not a great example.

    All these accusations are just the result of a massive right-wing campaign against facts and reality-based reporting. Everything that doesn’t follow their propaganda is biased, according to them.




  • This does sound very interesting. I should have said the debuggers I’m familiar with don’t do it. Or if they do, I have no idea how.

    Certainly setting breakpoints on certain conditions instead of just a line, would help a lot. Being able to step backwards through the execution even more so.


  • I can also see the variables change by logging them.

    Debuggers are great if you want to see in detail what’s going on in a specific loop or something, but across a big application with a framework that handles lots of things in unreadable code, multiple components modifying your state, async code, etc.; debuggers are a terrible way to track what’s going on.

    And often when I’ve found where it goes wrong, I want to check what was happening in a previous bit of code, a previous iteration or call. Debuggers don’t go back; you have to restart and run through the whole thing, again finding exactly where it went wrong, but now just a bit before that, which is often impossible.

    With logging, you just log everything, print a big warning where the thing has gone wrong, and scroll back a bit.

    Debuggers are a fantastic bit of technology, but in practice, simple logging has helped me far more often. That said, there are issues where debuggers do beat logging, but they’re a small minority in my experience. Still useful to know both tools.