Sara Ford talks with Dave Rael about developer productivity, learning to use your tools, disappointment, and deep human connections
Sara Ford is back at Microsoft on the Azure Identity team! Previously, she worked at GitHub and Microsoft... a couple of times. Sara started her career working on Microsoft's developer tools, including Visual Studio and CodePlex. She's authored a couple of books on Visual Studio with Microsoft Press. In 2015, Sara received her Masters degree in Human Factors (HCI / UX) at San Jose State University because she wants to make developer tools more usable. Sara's life-long dream is to be a 97-year-old weightlifter so she can be featured on the local news.
Chapters:
- - Dave introduces the show and Sara Ford
- - Sara on her focus on productivity with developer tools
- - Sara's interest in aviation and discovering computers and software
- - Confidence, assertion, and fear, asking for needed help, and the difference made by showing interest in people
- - Developing an interest in software and finding a great mentor and many motivations
- - The importance of people and relationships
- - Sara's success story - authoring a book and the deep significance of the experience in Sara's life
- - Sara's prediction for the future of software
- - Sara's top 3 tips for delivering more value
- - Keeping up with Sara
Resources:
- Sara's Blog
- Sara's Old Blog on MSDN Blogs
- Sara on GitHub
- Microsoft Visual Studio Tips - Sara Ford
- Design Patterns: Elements of Reusable Object-Oriented Software - Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides
- Sara's Git(Hub) Tip of the Day Blog Series
- Space Shuttle Challenger
- Challenger: President Reagan's Challenger Disaster Speech - 1/28/86
- Early Decision
- Denise Jacobs on Developer On Fire
- Carin Meier on Developer On Fire
- "To try and fail is at least to learn; to fail to try is to suffer the inestimable loss of what might have been." - Chester Barnard
- Chester Barnard
Sara's book recommendation:
Sara's top 3 tips for delivering more value:
- Identify and take the next step
- Separate your inner product manager from you inner developer (and listen to the PM)
- Don't procrastinate