Here are some YouTube channels to check out

Developer Related

• Primeagen - High-energy, chaotic programming and tech commentary
• Theo - t3.gg - Funny, soft spoken, and deeply technical
• Nick Capsas - Clear, in-depth tutorials on C# and .NET development
• LaurieWired - Technical, educational content about reverse engineering, decompilation, and malware analysis

IMO Primeagen / Theo is a Coke vs. Pepsi preference. Nick and Laurie are also great.

Cyber Security / Cryptography / Digital Privacy

• Low Level - C programming, computer architecture, and cybersecurity
• Addie LaMarr - Cybersecurity, digital self-protection, career guidance, and neurodiversity advocacy
• Hak5 - Cybersecurity tutorials, ethical hacking, and cutting-edge penetration testing gear.

Agile / Development Process

• Modern Software Engineering - Thoughtful, expert-led discussions, tutorials, and case studies on software development best practices

General Tech

• Goda Go - Practical, accessible ways to use AI tools and build AI systems
• Shannon Morse - Tech reviews, cybersecurity and privacy tutorials, tech advice, and industry news
• Anastasi In Tech - Advanced hardware engineering, chip design, AI technologies, and semiconductor trends

I love this list by Signs of Triviality so I thought I would ask Perplexity for a few examples.

1. Conway’s Law

“You will ship your org chart.”

Spotify Example: Squads, Tribes, and Microservices

Spotify intentionally designed its organization into Squads, Tribes, Chapters, and Guilds – small, cross-functional, semi-autonomous teams responsible for specific features or functions of the product. This team structure mirrors the company’s modular, microservice-based architecture, where each service is independently developed, deployed, and maintained by the squad that owns it.

2. Brooks’s Law

“Adding manpower to a late software project makes it later.”

The Mythical Man-Month

One of the best-documented examples comes directly from Fred Brooks’s own experience managing IBM’s OS/360 project in the 1960s. As the project began to run behind schedule, management added more programmers to speed up progress. Instead, the project suffered further delays due to the ramp-up time required to train new developers and the exponential growth in communication overhead. This experience led Brooks to formulate his law in The Mythical Man-Month.

3. Zawinski’s Law

“Every program attempts to expand until it includes a web server. Those programs which cannot so expand are replaced by ones which can.”

A clear modern demonstration of Zawinski’s Law—the idea that “every program attempts to expand until it can read mail; those programs that cannot so expand are replaced by ones that can”

Example: Slack’s Expansion

Slack originally launched as a simple team chat app designed for fast internal communication. Over time, it evolved into a complex work hub by integrating file sharing, video calls, automation workflows, and a marketplace of third-party apps. This expansion gained users but also introduced feature bloat, with critics noting that Slack became less focused and more resource-intensive—an embodiment of Zawinski’s Law at work. The company expanded communication beyond chat, effectively trying to “read mail” in the metaphorical sense.

Open source software is not always “cheaper” in the long run because it is “free”, but it can provide a distinct advantage for solving novel and unique problems.

Many small businesses believe that it’s too expensive to outsource most of the day to day technical headaches.