John Baluka talks with Dave Rael about business and software, presence in daily activity, the power of mastermind groups, and creating useful content
John has been developing software with the Microsoft stack for 20+ years. For most of the last 10 years, John has been a sub-contractor, business owner, and a dad. John enjoys researching and applying new technologies to real world examples.
Chapters:
- - Dave introduces the show and John Baluka
- - John's business emphasis
- - Becoming fearless
- - John and subcontracting
- - John's experiences with Visual Basic and moving to C# - "It's okay to be a beginner"
- - The things that "light John up"
- - Becoming a speaker and creating content
- - Parallels between business and producing content - testing an audience to see if there is interest
- - John's story of failure - getting in too deep on borrowed funds
- - John's success story - delivering consistently, code generation that made life easier
- - How John stays current with what he needs to know
- - John's family
- - Getting better at presence
- - John's book recommendatons
- - The things that have John most excited
- - The concept of mastermind groups
- - John's top 3 tips for delivering more value
- - Keeping up with John
Resources:
- John On LinkedIn
- nopCommerce
- Cory House on Developer On Fire
- remarkjs
- John's Presentation - Hacking PowerPoint for Developers
- The Morning Brew - Chris Alcock
- The Pomodoro Technique
- Dave's Blog Post on the Pomodoro Technique
- John's completed Pluralsight Courses
- John Papa's Pluralsight Courses
- John Papa on Developer On Fire
- Julie Lerman's Pluralsight Courses
- Pluralsight Course - Jeff Ammons - Build a Better Blog with a Static Site Generator
- DH Unplugged
- Pam Selle on Developer On Fire
- Go the F*** Home - Pam Selle's Talk on Getting it Done and Living Life
- Startups for the Rest of Us (Podcast with Rob Walling)
- MastermindJam
- James Sturtevant on Developer On Fire
John's book recommendation:
John's top 3 tips for delivering more value:
- Marry the problem and not the solution
- Try not to create a solution that's looking for a problem to solve
- Weekly milestones help better manage the workflow for everyone involved