Developer on Fire
Developer on Fire
Episode 275 | Ken Versaw - Doing What Is Needed
Guest:
Ken Versaw talks with Dave Rael about life-improving experiences at conferences, automation, solving problems, and taking action
Ken Versaw is a co-founder and CEO of Amegala, an organization dedicated to creating high-quality, community-focused training and networking opportunities for software development professionals.
Chapters:
- - Dave introduces the show and Ken Versaw
- - Staring with Nebraska CodeCamp and growing to an organization with multiple multi-day events
- - The life-altering experiences of developer conferences
- - Ken's experiences hearing from conference attendees about benefits
- - Social experiences for developers
- - Ken's current software interest and projects
- - How Ken stays current with what he needs to know
- - How Ken got started in software
- - How Ken and Adam Barney became connected and started working together
- - Identifying things that need to be done and doing them
- - Ken's story of failure - Facing hostile criticism of Nebraska CodeCamp inclusivity
- - Ken's success story - becoming a software developer by taking a shot on scripting a task rather than manual execution
- - Ken's book recommendation
- - The things that have Ken most excited
- - Ken's causes of pain and suffering
- - Ken's top 3 tips for delivering more value
- - Keeping up with Ken
Resources:
- Amegala
- VS Live!
- Adam Barney
- Nebraska.Code()
- Detroit.Code()
- Indy.Code()
- Prairie.Code()
- Kansas City Developer Conference
- SOLID Design Principles
- Cory House on Developer On Fire
- Lee Brandt on Developer On Fire
- Jon Mills on Developer On Fire
- Boon Lee
- Shawn Rakowski on Developer On Fire
- Phaser.js
- Compact disc
- George McFly and the Fear of Rejection
- Omaha World Herald - 48 Men. No women. How a local event's speaker list came to look like 1964
- Podcast: Waking Up with Sam Harris
Ken's book recommendation:
Ken's top 3 tips for delivering more value:
- Break a problem down into small pieces and get the small pieces of software in front of users as quickly as possible
- Listen to feedback
- Change your beliefs quickly when you encounter conflicting evidence
