Developer on Fire
Developer on Fire
Episode 079 | Greg Shackles - Not Just Mobile
Guest:
Greg Shackles talks with Dave Rael about valuable user experiences, the art of unit testing, and understanding users
Greg Shackles is a Principal Engineer at Olo. He is a Xamarin MVP, Microsoft MVP, host of the Gone Mobile podcast, organizer of the NYC Mobile .NET Developers Group, author of Mobile Development with C#, and also a monthly columnist with Visual Studio Magazine.
Chapters:
- - Dave Introduces the show and Greg Shackles
- - What is Xamarin?
- - Greg's intorduction to Xamarin and its predecessors
- - Greg's definition of value
- - Lessons from observing a spouse - typical users often blame themselves for failings in software
- - The things that "light Greg up"
- - Greg's story of failure - "DevOops" - Infinite recursion, underestimating the fix
- - Greg success story - Blogging and speaking, engaging communities
- - How Greg stays current with what he needs to know
- - Greg's book recommendation
- - The things about which Greg is most excited
- - Greg's greatest sources of pain
- - The things about which Greg likes to geek out apart from software
- - Home Brewing feedback cycles
- - Greg's history with making music
- - Greg's prediction for the future of software
- - Greg's top 3 tips for delivering more value
- - Keeping up with Greg
Resources:
- Greg's Blog
- Gone Mobile - Greg's Podcast
- NYC Mobile .NET Developers Group
- Greg's Book: Mobile Development with C#: Building Native iOS, Android, and Windows Phone Applications
- Xamarin
- PEBKAC (Problem Exists Between Keyboard and Chair)
- iBeacon
- Uber
- myEcho
- Scott Hanselman
- Hofstadter's law
- John Zablocki
- Cory House on Developer On Fire
- Jessica Kerr on Developer On Fire
- Troy Hunt on Developer On Fire
- Greg's post about Courier Location Tracking: Caviar Is Cavalier About Privacy
- Ted Neward on Developer On Fire
- MvvmCross
Greg's book recommendation:
Greg's top 3 tips for delivering more value:
1. Start blogging and speaking
2. Make sure you understand the user of your software - exercise empathy
3. Read as much code as you can
2. Make sure you understand the user of your software - exercise empathy
3. Read as much code as you can
