In this conversation, Matt and Ken are joined by Floyd May, a software engineer with over 20 years of experience. They discuss Floyd's journey in software development, the challenges faced by new developers, and the importance of empathy and communication in software engineering. Floyd also shares his insights on setting up software engineers for success and the benefits of continuous deployment and mentorship. In this conversation, the host and guest discuss the importance of mentorship in software development and the benefits of a one-on-one mentorship model. They also explore the value of continuous learning, the role of communication skills in software engineering, and the significance of automated testing. The guest shares his criteria for finding apprentices and emphasizes the need for developers to pace themselves and prioritize learning. He recommends three books for software engineers: 'Refactoring' by Martin Fowler, 'Domain Driven Design' by Eric Evans, and 'The Software Architect Elevator' by Gregor Hopa.


Takeaways:

• New developers often lack core skills like source control, design patterns, and unit testing, which can be addressed through mentorship and hands-on experience.
• Closing the gap between software engineers and end users requires frequent communication and continuous deployment.
• Understanding the problem and empathizing with the users is crucial for successful software development.
• The project-oriented mindset is becoming less effective, and a design-oriented approach with continuous feedback and involvement of stakeholders is more beneficial.
• Junior developers can benefit from a mentorship model, where they are given the opportunity to learn and grow while being supported by experienced engineers. One-on-one mentorship is highly effective in software development, allowing for personalized guidance and knowledge transfer.
• Continuous learning is crucial for software engineers to stay updated and improve their skills.
• Communication skills are essential for senior-level developers, including mentoring others and effectively communicating with clients.
• Automated testing is important for insulating software from bugs and reducing the need for manual testing.
• Developers should pace themselves and prioritize learning, building small consistent habits over time.
• Recommended books for software engineers: 'Refactoring' by Martin Fowler, 'Domain Driven Design' by Eric Evans, and 'The Software Architect Elevator' by Gregor Hopa.

Sound Bites:

• "I get the most rewarding experience out of actually getting to talk to people that use the stuff that I build and interacting with them."
• "The only thing that I've ever seen actually be effective in closing that gap is direct one-on-one mentorship."
• "Continuous deployment makes it a whole lot easier to have a meaningful conversation with a user because that conversation now gets to be in the context of here's the software, you can touch it, you can interact with it, you can play with it."
• "I think that in general, most people learn the best when they're dealing with someone that already knows what they're doing."
• "I was the most successful personally when I took the time to read books, read blog articles, read documentation instead of just reaching for the code editor first thing."
• "You're winning if you're learning. I'll figure out how to make it profitable."

Chapters:
00:00The Journey in Software Development
07:01Challenges Faced by New Developers
13:13The Importance of Empathy and Communication
17:31Setting Up Software Engineers for Success
21:41The Benefits of Continuous Deployment
24:29The Mentorship Model for Junior Developers
26:26The Importance of Continuous Learning
29:06The Significance of Automated Testing
31:28Pacing and Prioritizing Learning
43:01Recommended Books for Software Engineers