Developer on Fire
Episode 370 | John Wright - Getting Involved
John M. Wright has been a professional software developer for about 18 years, gaining experience ranging from “shrink-wrapped” software to large, distributed networks using multiple platforms and technologies. His experience spans the entire software lifecycle, from customer-facing requirements gathering, through development and release, and continued maintenance. Though he has experience in a management role, his passion lives in writing high-quality, clean code while providing leadership through technical direction and mentorship. He enjoys sharing his experiences with automated testing, mocking frameworks, and static analysis tools, or guiding other developers through the darker crevices of the .NET framework, while also learning from his peers’ experiences -- helping everyone "level up" as a team. He has a pragmatic approach to and a heavy interest in continuous improvement of people, process, and product. He's currently applying that experience as a Full-Stack Web Developer at Stack Overflow on the Internal Development team.
Chapters:
- - Dave introduces the show and John Wright
- - John on getting involved in being a conference speaker
- - Expectations for being a speaker vs reality
- - John working at Stack Overflow
- - The broader Stack Exchange network
- - Stack Overflow and .NET Core
- - John's story of failure - exposing a bug that gave away free service
- - John's book recommendations
- - John's top 3 tips for delivering more value
- - Keeping up with John
Resources:
- John's Blog
- THAT Conference
- Steven Hicks on Developer On Fire
- David Neal on Developer On Fire
- KCDC - Kansas City Developer Conference
- Jay Harris on Developer On Fire
- Christina Aldan
- Chad Green
- Joel Spolsky
- The Joel Test
- Nick Craver
- Marc Gravell
- The Story of Thomas Watson mistakes, firing, and education
- Design Patterns: Elements of Reusable Object-Oriented Software - Erich Gamma
- Rob Conery on Developer On Fire
John's book recommendation:
John's top 3 tips for delivering more value:
- It's OK to fail
- Be aware of burnout - don't suffer in silence
- Understand the business and how people are using your software