While cleaning out his office, Mr. Fred uncovers a 3.5-inch floppy disk labeled “Y2K Startup Disk”, a quiet reminder of a moment when computers around the world were about to be confused by time itself.
In this episode of Mr. Fred’s Tech Talks, we revisit what the Y2K problem actually was, why it mattered, and how engineers addressed a design decision that had been quietly waiting to fail. From there, Mr. Fred connects that moment to the next major time-based computing challenge: the Year 2038 problem.
You’ll learn how Unix systems track time, why 32-bit limits matter, which systems could still be affected, and whether this issue is already being addressed. This episode is a thoughtful explainer for tech professionals, educators, students, and curious listeners who want to understand how past assumptions shape today’s technology.
Show NotesIn this episode, Mr. Fred explores how time can quietly break computers and what we can learn from it.
Topics include:
- What a 3.5-inch floppy disk is and why it mattered
- What the Y2K problem really was (and wasn’t)
- Why early design shortcuts made sense at the time
- How Unix systems store time
- What the Year 2038 bug is and how it compares to Y2K
- Which systems may still be affected
- Whether engineers are already addressing the issue
- A simple takeaway for younger listeners learning how computers work
This episode isn’t about fear, it’s about understanding systems, assumptions, and why good engineering means revisiting old decisions.
CONNECT
Website: https://www.getmecoding.com
Courses: https://courses.getmecoding.com
FOLLOW
YouTube: https://www.youtube.com/@GetMeCoding
Instagram: https://www.instagram.com/getmecoding
Facebook: https://www.facebook.com/GetMeCoding
LinkedIn: https://www.linkedin.com/in/mrfred77/
Follow, rate ★★★★★, and share!
Hosted on Acast. See acast.com/privacy for more information.