Suggestions
Steve Kuo
Consummate Code Crafter
Steve Kuo is the Director, Technical Coach at Salesforce, a role he began in early 2024. He has a rich background in software development, coaching, and organizational transformation, particularly in the realm of Agile methodologies and Extreme Programming (XP) principles. His career spans various industries including telecommunications, finance, and retail, where he has successfully led teams through significant transformations.13
Professional Background
- Experience: Steve has been instrumental in changing how organizations approach software development and team dynamics. He has a proven track record of improving team performance and delivering high-quality software solutions. Notably, he transformed a struggling bi-continent department into a high-performing unit recognized for its efficiency and quality.1
- Coaching and Mentoring: As a mentor and facilitator, Steve emphasizes the importance of sustainable work practices and continuous learning. He actively participates in community initiatives like the Seattle Code Crafters meetup, which focuses on enhancing coding skills among local developers.12
Community Engagement
Steve is committed to fostering a culture of learning within the software community. He organizes events such as Global Day of CodeRetreats and speaks at various conferences on topics related to collaborative programming, hiring practices, and Agile methodologies.13
Personal Life
Outside of his professional commitments, Steve enjoys outdoor activities such as hiking, cycling, and kayaking. He values work-life balance and spends quality time with his family.1
In summary, Steve Kuo's role as Director at Salesforce reflects his dedication to technical excellence and community engagement in the software industry.
Highlights
Quick question, why are mocking frameworks bad?
#1 I'm of that mindset and don't use them, but I'm running out of reasons why and looking for more ways to address "Why are they bad, I use them thousands of times every day!"
I heard very early on in my TDD career to not use mocking frameworks and they were bad. I kept trying to not use them but they were just so damn convenient. It wasn't until post the Fred George OOP Bootcamp that I realized HOW to not have them and how writing my own test doubles was imminently easier and offered a lot more flexibility.
Some of the reasons that I don't use mocking frameworks... They do too many things under the covers that cover up and lead to unintended consequences. No one uses VerifyAll() any more I frequently see mocks validating mocks They hide and make having code dependencies ok They enable bad coding behaviors Mocking Frameworks enable anti-SOLID behavior
What are your reasons for hating or not using mocking frameworks?
Tomorrow, Thursday Aug 21, at 10:00 AM join fellow Seattle Crafters to hear Amber Conville talk about "Leading Change from the Bottom"! Should be fabulous talk, come have some fun with us tomorrow.
https://lnkd.in/gCrFGJSp
