Brad

It took me 10 years in corporate to realize this and I'll tell you in 30 seconds (from someone who walked away): 1. If you stay in the 9-5 world too long, you end up being immature about how the world works.

A software engineer who wrote the code that landed humanity on the moon realized one terrifying truth: You cannot predict every error, but you can dictate exactly how the system reacts to them. Her name is Margaret Hamilton, the woman who famously coined the term "software engineering." She argued that we obsess over writing perfect code and completely ignore how the system handles catastrophic failure. Here are 4 operational frameworks she used to build elite, fault-tolerant architecture:

You probably weren’t told this, but… Your laptop is keeping a travel diary of everywhere you have been for the last 5 years. It’s called WLAN-AutoConfig. Every time you connect to WiFi, Windows logs: SSID (the network name) BSSID (the router’s MAC) Timestamp of the connection Those entries sit in your saved profiles and WLAN event logs. Most people never clear them. And here’s the problem: A BSSID is a physical device ID. Crowdsourced databases like WiGLE(@wiglenet) map millions of BSSIDs to real-world coordinates. So a forensic analyst doesn’t need a location tracker. They just dump your WiFi history… Plug those MACs into a database… And instantly reconstruct a map of where your laptop has been. 💀

𝟭𝟱 𝗕𝗲𝘀𝘁 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝗕𝗼𝗼𝗸𝘀 I was often asked which leadership resources I could recommend, so here is the list of 15 leadership books that had the most influence on me: 𝟭. 𝗛𝗼𝘄 𝗧𝗼 𝗪𝗶𝗻 𝗙𝗿𝗶𝗲𝗻𝗱𝘀 𝗮𝗻𝗱 𝗜𝗻𝗳𝗹𝘂𝗲𝗻𝗰𝗲 𝗣𝗲𝗼𝗽𝗹𝗲 A classic from 1936. Still very true today. How to advise in communication and influence. 𝟮. 𝟳 𝗛𝗮𝗯𝗶𝘁𝘀 𝗼𝗳 𝗛𝗶𝗴𝗵𝗹𝘆 𝗘𝗳𝗳𝗲𝗰𝘁𝗶𝘃𝗲 𝗣𝗲𝗼𝗽𝗹𝗲 It was first published in 1990 and is considered a classic. It teaches how to apply a principle-centered approach to solving life's challenges. 𝟯. 𝗥𝗮𝗱𝗶𝗰𝗮𝗹 𝗖𝗮𝗻𝗱𝗼𝗿 An innovative approach to leadership, how to care personally, and challenge directly. 𝟰. 𝗣𝗿𝗶𝗺𝗮𝗹 𝗟𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 This book explores the concept of emotional intelligence in the business world, a skill every leader needs. 𝟱. 𝗛𝗶𝗴𝗵 𝗼𝘂𝘁𝗽𝘂𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 One of my favorite books by Andrew Grove provides a comprehensive overview of a manager's role. 𝟲. 𝗧𝘂𝗿𝗻 𝘁𝗵𝗮𝘁 𝗦𝗵𝗶𝗽 𝗔𝗿𝗼𝘂𝗻𝗱 This is a book about great leadership styles applied in a submarine. It explains that everyone can be a leader. 𝟳. 𝗘𝘅𝘁𝗿𝗲𝗺𝗲 𝗢𝘄𝗻𝗲𝗿𝘀𝗵𝗶𝗽 The book explains that you must own everything if you're a leader, and there is no one else you can blame. 𝟴. 𝗟𝗲𝗮𝗱𝗲𝗿𝘀 𝗘𝗮𝘁 𝗟𝗮𝘀𝘁 A famous piece by Simon Sinek argues that leaders should sacrifice their comfort to benefit those who follow them. 𝟵. 𝗖𝗿𝗲𝗮𝘁𝗶𝘃𝗶𝘁𝘆 𝗜𝗻𝗰 This book describes how building great teams requires humility and how we can learn from and embrace failure. 𝟭𝟬. 𝗘𝗺𝗼𝘁𝗶𝗼𝗻𝗮𝗹 𝗜𝗻𝘁𝗲𝗹𝗹𝗶𝗴𝗲𝗻𝗰𝗲 A book based on Daniel Goleman's research offers new insights into two minds, rational and emotional. 𝟭𝟭. 𝗧𝗵𝗲 𝗙𝗶𝘃𝗲 𝗗𝘆𝘀𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 𝗼𝗳 𝗮 𝗧𝗲𝗮𝗺 The books describe five dysfunctions of a team and help leaders avoid failures. 𝟭𝟮. 𝗡𝗼𝗻𝗩𝗶𝗼𝗹𝗲𝗻𝘁 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 A book describes how we can be compassionate with ourselves and others. 𝟭𝟯. 𝗧𝗵𝗲 𝗠𝗮𝗸𝗶𝗻𝗴 𝗼𝗳 𝗮 𝗠𝗮𝗻𝗮𝗴𝗲𝗿 It explores what new managers can do in their first three months and beyond to ensure their team gets excellent results. 𝟭𝟰. 𝗗𝗿𝗶𝘃𝗲 The author suggests that great leaders should provide their teams with skills & a sense of purpose. 𝟭𝟱. 𝗚𝗼𝗼𝗱 𝗱𝗼 𝗚𝗿𝗲𝗮𝘁 The book is based on the premise that "good is the enemy of great." Also, for all tech leads, I could recommend "Elastic Leadership: Growing Self-organizing Teams" by Roy Osherove. 👉 Read more: newsletter.techworld-with-milan.com/p/15-best-lead…

A positive work culture is not: 🔴 Free meal 🔴 Free coffee 🔴 Ping-pong table 🔴 Gym membership 🔴 Unlimited snacks 🔴 Fancy office parties Companies use these perks to attract people. But perks alone don't make a workplace great. What truly matters to employees is: ✅ Autonomy in how they do their work (and from where) ✅ Clear expectations and well-defined processes ✅ Leaders who listen, support, and inspire ✅ Real opportunities for professional growth ✅ Trust and flexibility when life happens (you have private stuff, just do it, don't ask for permission) ✅ Genuine appreciation for their contribution Perks might get people through the door, but meaningful work and respect keep them there.

𝗗𝗲𝘃𝗢𝗽𝘀 𝗮𝘀 𝗮 𝗕𝘂𝗿𝗴𝗲𝗿 (𝗗𝗮𝗮𝗕) What should the DevOps engineer's roadmap look like: 𝟭. 𝗟𝗲𝗮𝗿𝗻 𝗮 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲 (Python, Go, ...) to write automation scripts 𝟮. 𝗠𝗮𝘀𝘁𝗲𝗿 𝗼𝗻𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘀𝘆𝘀𝘁𝗲𝗺 (Linux) and its command-line interface (CLI) 𝟯. 𝗠𝗮𝘀𝘁𝗲𝗿 𝘀𝗲𝗿𝘃𝗲𝗿 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁, web servers, including proxies such as Nginx or IIS 𝟰. 𝗘𝘅𝗽𝗹𝗼𝗿𝗲 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝘂𝘀𝗶𝗻𝗴 𝗗𝗼𝗰𝗸𝗲𝗿 𝟱. 𝗖𝗵𝗲𝗰𝗸 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝟲. 𝗨𝗻𝗹𝗼𝗰𝗸 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗮𝘀 𝗖𝗼𝗱𝗲 (IaC) using tools like Terraform, Ansible, Chef, or Puppet for provisioning and configuration management 𝟳. 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗻𝗲𝘁𝘄𝗼𝗿𝗸 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: DNS, IP addresses, ports, and the OSI model 𝟴. 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻/𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 (𝗖𝗜/𝗖𝗗) 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 for automating app delivery and deployment stages 𝟵. 𝗠𝗮𝘀𝘁𝗲𝗿 𝗺𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀 for real-time oversight of applications, services, and infrastructure 𝟭𝟬. 𝗚𝗮𝗶𝗻 𝗵𝗮𝗻𝗱𝘀-𝗼𝗻 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝘄𝗶𝘁𝗵 𝗖𝗹𝗼𝘂𝗱 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿𝘀 like AWS and Azure. To learn more about it, check out my complete DevOps roadmap for 2025 in the comments. #technology #softwareengineering #programming #techworldwithmilan #devops

BREAKING: MIT just completed the first brain scan study of ChatGPT users & the results are terrifying. Turns out, AI isn't making us more productive. It's making us cognitively bankrupt. Here's what 4 months of data revealed: (hint: we've been measuring productivity all wrong)

𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗟𝗮𝘄𝘀 𝗬𝗼𝘂 𝗠𝘂𝘀𝘁 𝗞𝗻𝗼𝘄 Here is the list of the most crucial software engineering laws you should know: 𝟭. 𝗣𝗮𝗿𝗸𝗶𝗻𝘀𝗼𝗻’𝘀 𝗟𝗮𝘄 - "Work expands to fill the available time." Tasks tend to take up as much time as allocated. Setting realistic deadlines helps avoid unnecessary scope and work expansions. Without clear boundaries, teams might spend more time than necessary, delaying project completion. 👉 Why it matters: Set precise deadlines to maintain focused effort and avoid wasted resources. 𝟮. 𝗛𝗼𝗳𝘀𝘁𝗮𝗱𝘁𝗲𝗿’𝘀 𝗟𝗮𝘄 - "It always takes longer than you expect, even when accounting for Hofstadter’s Law." Software development estimates are often optimistic. Even when you factor in delays, unexpected complications arise. Adding generous buffers can mitigate unrealistic expectations. 👉 Why it matters: Always add buffers to your estimates to manage expectations and prevent burnout. 𝟯. 𝗕𝗿𝗼𝗼𝗸𝘀’ 𝗟𝗮𝘄 - "Adding manpower to a late software project makes it later." Increasing team size late in a project adds overhead, as new members require a ramp-up period, and improved communication is necessary. This overhead can further slow down progress. 👉 Why it matters: Optimize your existing team's efficiency rather than expanding late in a project. 𝟰. 𝗖𝗼𝗻𝘄𝗮𝘆’𝘀 𝗟𝗮𝘄 - "Organizations design systems mirroring their communication structure." The product architecture reflects team structures and communication patterns. Aligning your organizational structure with your desired system architecture ensures cohesive and efficient designs. 👉 Why it matters: Structure teams to reflect desired product outcomes, ensuring clear and effective communication. 𝟱. 𝗖𝘂𝗻𝗻𝗶𝗻𝗴𝗵𝗮𝗺’𝘀 𝗟𝗮𝘄 - "The best way to get the right answer is not asking a question, but posting the wrong answer." People are quick to correct errors. By proactively engaging with imperfect solutions, you prompt rapid feedback and knowledge transfer, which resolves issues more quickly. 👉 Why it matters: Post imperfect solutions to prompt quicker feedback and knowledge sharing. 𝟲. 𝗦𝘁𝘂𝗿𝗴𝗲𝗼𝗻’𝘀 𝗟𝗮𝘄 - "90% of everything is crap." Most ideas, code, or features add little value. Rigorous prioritization ensures efforts focus on high-impact areas, significantly benefiting overall productivity and project outcomes. 👉 Why it matters: Prioritize rigorously and focus efforts only on the most impactful features. 𝟳. 𝗭𝗮𝘄𝗶𝗻𝘀𝗸𝗶’𝘀 𝗟𝗮𝘄 - "Every program expands until it can read mail." Software tends to grow unnecessarily complex by continuously adding features. Vigilance against feature creep helps maintain simplicity, clarity, and user satisfaction. 👉 Why it matters: Regularly review and cut unnecessary features to maintain simplicity and usability. #softwareengineering #programming #coding

32 years ago today on June 9th 1993, the Montreal Canadiens won the Stanley Cup. Here’s the call by the legendary Bob Cole.

Share this with anyone who still doesn't understand the tariffs

𝗗𝗲𝘃𝗢𝗽𝘀 𝗮𝘀 𝗮 𝗕𝘂𝗿𝗴𝗲𝗿 (𝗗𝗮𝗮𝗕) What should the DevOps engineer roadmap look like: 𝟭. 𝗟𝗲𝗮𝗿𝗻 𝗮 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗹𝗮𝗻𝗴𝘂𝗮𝗴𝗲 (Python, Go, ...) to write automation scripts 𝟮. 𝗠𝗮𝘀𝘁𝗲𝗿 𝗼𝗻𝗲 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘀𝘆𝘀𝘁𝗲𝗺 (Linux) and its command-line interface (CLI) 𝟯. 𝗠𝗮𝘀𝘁𝗲𝗿 𝘀𝗲𝗿𝘃𝗲𝗿 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁, web servers, including proxies such as Nginx or IIS 𝟰. 𝗘𝘅𝗽𝗹𝗼𝗿𝗲 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝘂𝘀𝗶𝗻𝗴 𝗗𝗼𝗰𝗸𝗲𝗿 𝟱. 𝗖𝗵𝗲𝗰𝗸 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗼𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 𝟲. 𝗨𝗻𝗹𝗼𝗰𝗸 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗮𝘀 𝗖𝗼𝗱𝗲 (IaC) using tools like Terraform, Ansible, Chef, or Puppet for provisioning and configuration management 𝟳. 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗻𝗲𝘁𝘄𝗼𝗿𝗸 𝗽𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀: DNS, IP addresses, ports, and the OSI model 𝟴. 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻/𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 (𝗖𝗜/𝗖𝗗) 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 for automating app delivery and deployment stages 𝟵. 𝗠𝗮𝘀𝘁𝗲𝗿 𝗺𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝘁𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲𝘀 for real-time oversight of applications, services, and infrastructure 𝟭𝟬. 𝗚𝗮𝗶𝗻 𝗵𝗮𝗻𝗱𝘀-𝗼𝗻 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝘄𝗶𝘁𝗵 𝗖𝗹𝗼𝘂𝗱 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗿𝘀 like AWS and Azure. #programming #devops #developers

Listen to this. Absolutely true and couldn’t have said it better myself. Seriously, EVERY Canadian needs to hear this.

This may be the greatest fucking hockey card ever. I’m savoring it as one would a glass of fine wine. I detect notes of mullet, Cooperalls, and a Camaro with tinted windows awaiting him in the parking lot.

Naval Ravikant cracked the code on wealth and happiness. But most people struggle their entire lives because they ignore his wisdom. Don't let that be you. These 6 life-changing insights will shift your mindset forever🧵:

@alancross Probably best to focus on music. Not a tasteful post.

It’s only January 1 and we have THE perfect picture for all of 2025.

Charles Bukowski shocked the world in 1987. He finally became famous for writing about modern American life that included extreme violence & s*x acts. I spent the last 5 years digesting it all... And these are the 14 things I can't stop thinking about:

Thread on the real size of things 🧵 1. Titanic compared to a modern cruise ship

Thread of cool maps you've (probably) never seen before 🧵 1. All roads lead to Rome

You know what should make you scratch your head? Many of the companies hit by the CrowdStrike outage are classified as critical infrastructure. They probably had all kinds of certifications and were compliant with the highest security standards. Just recently, someone told me that in the last 10 ransomware cases they worked on, all 10 companies had ISO27001 certification. Some victims from the banking sector even complied with stricter guidelines and additional certifications. It makes you wonder about the actual positive impact of these certifications if the organization doesn't truly live and breathe those standards in all processes and minds. And for the CrowdStrike case, I bet many didn't include the risk 'our EDR agent crashes all the machines it's running on' in their risk assessments.