Jack's Rants - Why You Need to Reboot : Why Rebooting Your Computer Actually Fixes Problems

"Have you tried turning it off and on again ?" became an IT cliché for a reason. Rebooting clears accumulated state, resets resources, and fixes a surprising number of problems.
From Unix uptime bragging rights to mainframe IPLs and Windows servers nobody is allowed to restart, every system has its own relationship with rebooting. Maybe what we really need is a reboot SLA.

Want even more info ? Read our show notes and related blog post related to this episode : https://blog.ithorrorstories.eu/jacks-rants-can-i-keep-your-id/

00:00 Introduction
02:17 Developer Habits
04:01 Mainframes & Servers
06:18 Reboot Realities
08:19 Conclusion

Testing software sounds simple enough. But what exactly should you test, where should those tests happen, and how do you decide which parts of a complex system need the most attention?

Jack talks with Mooly Beeri about software testing from a developer's perspective: identifying the right test points, understanding how different parts of a system interact, and building testing into the development process rather than treating it as something that happens at the end. A practical look at what it actually means to test software properly.

You can read more from Mooly at https://www.bettersoftware.dev/

Want even more info ? Read our show notes and related blog post related to this episode : https://blog.ithorrorstories.eu/episode-21-testing-software-properly/

00:00 Introduction
01:05 Mooly's Background
01:43 Automotive Software
04:01 Software Challenges
06:21 Bug Management
12:11 Improving Processes
15:42 Communication Importance
28:07 Summary

One day, a busy IBM-compatible mainframe began slowing to a crawl. Hundreds of programmers noticed immediately—some even resorted to banging on the server room window whenever the system became unusable. The problem appeared after a microcode upgrade, but nothing pointed to an obvious cause.

In this episode, Jack Smith talks to Matt about an extraordinary piece of low-level troubleshooting that led deep into the internals of VM, interrupt handling and timer queues. Armed with nothing more than hex dumps, careful reasoning and a willingness to modify live memory, Matt uncovered a vendor bug and devised a temporary workaround that kept the system running until a permanent fix arrived. It's a fascinating story of how understanding a system at its lowest levels can solve problems that no diagnostic tool could explain.

Want even more info ? Read our show notes and related blog post related to this episode : https://blog.ithorrorstories.eu/episode-20-microcode-mayhem/

00:00 Introduction
01:07 Mainframe Tech
04:38 Microcode Issues
07:19 Timer Interrupts
15:02 Modern Comparisons
19:44 Final Insights
22:18 Conclusion