When Open Source Goes Wrong Tech Team Weekly

We're back for our second season! We're starting off with a dicussion about how we use open source software in our workplaces, after a couple of  major recent scares and outages. How do you keep track of what you're incorporating into your software, and how can we make sure that authors are rewarded for their efforts?

Plus, we update you on everything that's happened over our Christmas break: find out who caught COVID, who completed Red Dead Redemption 2, who's been won over by Microsoft Teams, and who's been donating to Wikipedia.

TIMESTAMPS:

00:00 Start
01:11 The Stand-Up
11:00 This Week's Epic
25:20 The Wash-Up

LINKS DISCUSSED THIS WEEK: 

Martin Fowler: Strangler Pattern

Google Support: Pixel 6 Pro rattling noise from camera

Entrepreneurial Operating System

Scaling Leaders

Herman Miller

TechCrunch: Open source developers, who work for free, are discovering they have power

Reddit: Author of Faker.js deletes the entire repo 

Lawfare: What's the Deal with the Log4Shell Security Nightmare?

The Register: Open source isn't the security problem – misusing it is

Buy Me A Coffee

GitHub: Danny Dainton - Newman Reporter HTMLExtra

Tech Times: Developer Gets Suspended After Intentionally Sabotaging GitHub and Other Open-Source Libraries

NBC New York: New Details in Case of Man Charged After NYC Fire, Potential Bomb-Making Materials Found

Google AMP


---

Send in a voice message: https://podcasters.spotify.com/pod/show/tech-team-weekly/message