Relentless Improvement for Software Development
Scott helped our successful software development team become more successful. He showed our team how greater productivity is achieved through software design, and challenged them to see the potential productivity pitfalls and communications barriers. He worked with our team, teaching our people to use behavior-driven development and test-driven design to improve our code, productivity, and communications. He helped our testers improve their ability to automate testing and become a more integral part of our product development process. Through Scott’s network we connected with people who would continue to help us improve and who would ultimately join the VersionOne team. Scott challenged us to go further than we’d come, and these challenges pay off.
Scott is a brilliant, passionate, driven and quality focused individual. He not only understands software, but he understands team dynamics and the mental model of end users. We’ve been extremely lucky to have his contributions to the Minggl vision and I hope to be among those extremely rare creatures who have proven him wrong, if only once!! I recommend him highly to all executives who need a passionate leader on their project.
Scott is one of those rare individuals with strong opinions, strong technical skills and experience, and a clarity of purpose and character that demands the highest expectations of himself and the people around him. Never have I met someone who is both so open-minded and yet so passionately outspoken. If people like me are priests of a technical religion, then Scott is the prophet in the wilderness, dressed in sackcloth and ashes, preaching to a growing community of people who want to see software ‘done right’. Anyone who is involved in the development of software, whether they agree with Scott or not, needs to listen to what he has to say.
Over the past couple of years, Scott has helped McLane to become a more agile software development organization. He has trained our people in contemporary software development techniques and approaches, and consulted with us on process and organization. Scott assisted us in positioning ourselves as a leading and progressive software development partner, working with us to communicate our abilities and capacities in bids, proposals, and in pitch meetings for customers. Scott has been a supporting player in our continuous transformation toward greater product development and solution agility and has inspired and challenged some of our senior people to new levels of achievement.
Scott worked with our team for two years, and in that time our development organization fundamentally transformed. We were a culture of individuals working in closed offices on disconnected projects. Now we’re an integrated product development group working together in a collaborative environment, using more effective ways of software design and development. I continue to learn from Scott in conversations about product design through a professional relationship that goes well beyond the work he did for us, and I continue to benefit from his insight and the community of professionals that he brings together for innovative events and exchanges. Scott came to our organization to introduce some contemporary software development techniques and left us on a whole new path pursuing new markets in new ways.
Prior to the workshop, no matter how much I was learning about Microservices, I never got any closer to solving the most fundamental, practical problems of the approach. No one was speaking or writing about how to actually accomplish the transition from the Monolith. Rather, everyone wanted to talk about peripheral issues like hosting or language. Eventide’s workshop actually addressed the most pressing and challenging topics of Microservices, namely the overarching principles and day-to-day tactics. I was actually experimenting with gold-standard examples, right there on my machine. I now feel able to assess Microservice approaches, avoid pitfalls and get my hands dirty. Unlike many other resources that explain the promises and perils of Microservices but fail to explain how to get there, Eventide’s workshop made it feel like a concrete realizable goal.
This workshop opened my eyes to the huge potential of evented backend systems and the true power of Ruby as a programming language. The material was well prepared and we got the chance to implement basic and advanced uses cases and patterns with Eventide.
The best part about Scott and Nathan’s approach to Event Sourcing is not that it works, but that they are placing emphasis on designing the foundation of your codebase as opposed to the shine of your tools.