📚 Resources 09 — Go Deeper on Bugs & Testing
All free. The first video is the natural companion to the lesson; the bug list is the rabbit hole; the rest are for anyone who felt a spark during the QA parts of the lab.
🎬 Watch
-
Crash Course Computer Science — “Software Engineering” & debugging topics — the Crash Course CS playlist covers how programs go wrong and how engineers keep large software correct, in the series’ trademark lively 10-minute style. Best for: reinforcing this module visually; the episodes around software engineering pair directly with this lesson.
-
CS50 (Harvard’s famous intro course) — lectures and shorts on testing and debugging — CS50 is Harvard’s legendary free introduction to computer science, and its material on debugging and testing (including the rubber duck — CS50 even built a virtual duck for students) is warm, funny, and rigorous. Best for: learners who want to see these ideas taught with live code, and anyone curious what a world-class university CS lecture feels like. Fair warning: CS50 moves faster than this course — dip in, don’t feel obliged to keep up.
đź“– Read
-
Wikipedia — “List of software bugs” — the famous catalog of history’s costly, deadly, and bizarre bugs: Knight Capital and the Mars Climate Orbiter are here, alongside rockets, radiation machines, and phone networks felled by single lines of code. Best for: everyone. It’s gripping, sobering, and each entry links to the full story. This page turns “all software has bugs” from a slogan into history.
-
Ministry of Testing — the largest community for software testers, with free articles, podcasts, and beginner guides to testing as a career. Best for: anyone who enjoyed writing the evil-inputs test plan in the lab more than they expected. That enjoyment is a real signal — QA is a genuine, well-paid path into tech that doesn’t start with heavy coding, and this community is its front door.
đź’ˇ One honest tip
If the lab’s bug hunt was fun, here’s a habit that costs nothing: whenever an app you use misbehaves, pause before restarting it and try to reproduce the problem — what exact steps make it happen every time? You’ll be practicing the first and hardest skill of debugging on real software, and you’ll start seeing edge cases everywhere. (Warning: this habit is permanent.)