@Sir Ryan BemroseIs that true or is she lying?:
In the video "Everything I learned at Microsoft in 9 Minutes", senior software engineer Maddy Zhang shares seven major lessons, engineering habits, and cultural rules she learned while working on Xamarin and Visual Studio at Microsoft.
Key Lessons Learned
1. Be a "Learn-It-All," Not a "Know-It-All" [00:01:05]
Under CEO Satya Nadella, Microsoft shifted away from a competitive, toxic internal ranking system toward a growth mindset. Engineers are encouraged to ask questions, admit when they do not know something, and prioritize continuous learning over maintaining an image of perfection.
2. Design for Someone You'll Never Meet [00:02:22]
Because Microsoft operates on a massive global scale (e.g., Windows on over a billion devices), software must be designed defensively. Engineers must account for slow connections, accessibility tools (screen readers), and localization (right-to-left languages) from the start.
3. Treat Backwards Compatibility as a Promise [00:03:28]
Microsoft goes to extreme lengths to avoid breaking existing user environments (such as adding custom OS logic so SimCity wouldn't crash on Windows 95). Once an API or interface is released, it should be carefully versioned and deprecated slowly rather than casually altered.
4. Bake Security into Every Line of Code [00:04:39]
Security is an upfront engineering responsibility rather than a final gate check. Following Microsoft's Secure Future Initiative (SFI), products should be secure by design, secure by default, and secure in operations.
5. Ship Fast and Learn from Real User Data [00:05:50]
Instead of trying to make everything perfect before launch, ship a functional version, track instrumented usage data, and refine based on actual user behavior rather than internal assumptions.
6. Embrace Constructive Criticism in Design Reviews [00:06:50]
Writing design docs and letting senior engineers critique them early prevents weeks of building the wrong solution. Feedback before writing core code surfaces edge cases, hidden dependencies, and simpler alternatives.
7. Stay Adaptable in the AI Era [00:07:35]
Tools and workflows change rapidly (highlighted by how internal developer tooling evolves quickly). Rather than mastering a single specific AI assistant or framework, developers should apply a "learn-it-all" mindset to continuously evaluate, adopt, and adapt to new technologies.