Part two of our interview with Douglas Squirrel delves into building real world software. This topic takes us into finding ways to meet a customer’s needs rather than deliver something that gets an “A” grade in academia. We also tackle the challenge of a technologist with a different view from the business customer. It is more focused on building relationships and trusts than it is asserting one’s opinion.
Real World Software Is Messy
There are almost always trade-offs when we talk about building a solution for business. We are not given the luxury of a perfect world and building a flawless solution. There is even a thing called “known bugs” included with many releases. We know at our core that perfect is not truly obtainable, so why stop a release to achieve that lofty objective? There is a better way to build software that accepts it as a work in progress and focuses on what can be delivered rather than perfection.
About Squirrel
Squirrel has been coding for forty years and has led software teams for twenty. He uses the power of conversations to create dramatic productivity gains in technology organizations of all sizes. Squirrel’s experience includes growing software teams as a CTO in startups from fintech to biotech to music and everything in between. He has consulted on product improvement at over 170 organizations in the UK, the US, Australia, and Europe. Also, he has provided coaching to various leaders in improving their conversations, aligning with business goals, and creating productive conflict. He lives in Frogholt, England, in a timber-framed cottage built in 1450.
