Do You Want Fries With That? From Punched Cards to DevOps and Beyond
summary
Argues that security is treated as an add‑on rather than built into developer workflows, using a staged punch‑card pipeline demo (analyst → coder → punch‑card operator → batch run) to show how physical constraints limited attacks, then traces tech changes that increase risk: early IBM System/360 runs at 1 MHz ≈ 35,000 ops/s, floppy disks make code portable so floppy disks enabled malware, and networked, desktop and distributed systems enlarge the attack surface and demand pipeline‑aware security practices.
AI-written summary · about
chapters (16)
- 0:00Secure software workflow
- 1:09Punched cards and batch programming
- 7:11Punch cards to real-time
- 13:10Margaret Hamilton origins
- 15:36Batch to real-time shift
- 17:20Floppy disks and portable software
- 20:13Mainframes to desktops
- 23:01Shrink-wrap software and e-commerce
- 25:13Accessibility and usability
- 26:35Cybersecurity concerns
- 29:25DevOps and modern developer role
- 30:52Computing education 1970s
- 33:15Security in academic curricula
- 37:29Industry developer training
- 39:2080-column line limits legacy
- 42:11Closing remarks and Q&A
related talks
31mDevOps: You Build It, You Secure It
25mKeynote: DevOps - The Return of Security
27mSecurity Learns to Sprint: DevSecOps
30mThe 3 Ways of DevSecOps – Making Shift Happen
39mDevOps: The Return of Security
47mThe Only Reason Security Really Matters for DevOps
39mThe Path Of DevOps Enlightenment For InfoSec
34mDevOps and Security: The Facts, The Myths, The Legend