This is Part 2 of TechTalk, and yeah… we got yeeted mid-stream because my internet decided to take a nap. YouTube has this insanely short 60–90 second timeout where if your connection drops, it just ends the live and you can’t “resume” it—even if OBS reconnects and says it’s streaming. So I’m walking through what happened with my Ziply outages (this is like the fifth one since the 8th), why it’s driving me nuts, and what the realistic workaround is (persistent stream keys, auto-reconnect, and basically accepting that you might end up with multiple parts). Then we get into the real meat: how AI is impacting jobs right now, not in some sci‑fi “one day” way, but in the “my friends at Microsoft and Google are getting laid off” way. I talk about how AI starts as an augmentation tool—especially for devs—and then quickly turns into a headcount reduction tool because managers notice the same work is getting done faster. I lay out the ugly progression: fewer devs, fewer code reviewers, then PMs getting replaced by AI agents, and eventually even directors just describing outcomes while the whole pipeline (dev, test, review, security) becomes automated. And I’m not speaking hypothetically—I’ve literally automated teams out of existence before. At Microsoft, I helped build Drive UI automation that took a manual test team of about 25 and basically reduced it to one person. The tech is cool, but the economic reality is terrifying, and that’s the conversation we’re having here.