Why I joined CodeLogic

I can’t count the times I’ve said, “You only need X if your software architecture is a mess… so pretty much everyone needs it.” Tools and processes can be powerful crutches to compensate for architecture problems, but they only take you so far. To get to the next level of improvements, teams need to move towards loosely coupled architectures, including cloud-native approaches. I want to support groups looking to understand and improve their architectures, and CodeLogic is a fantastic place to do that from.

Loosely coupled architectures are a significant multiplier in everything else you do. They simplify what a developer has to worry about while coding; they reduce the blast radius a tester has to worry about; they shrink the deployments' scope. To get the agility and quality we want, we keep inventing new ways to compartmentalize and decouple: everything from object-oriented programming to library dependency management like Maven or NPM, to API Gateways and Istio, have helped us loosen coupling at one level or another.  

CodeLogic excites me because it generates a dependency map of a software system that reveals the architecture in a brutally honest way. You can set up rules to detect potential architecture issues and more easily understand whether rearchitecting for speed is even viable in a given codebase. If we can tell people that rearchitecture is bleak, we can save them months of agony before the inevitable conversation about living with the status-quo versus rewriting.

As much as I love the technology, I’m even more excited to work with the incredible team over at CodeLogic. The CEO, Greg Wunderle, is a visionary leader while being a kind and decent person. I’m thrilled to go work for a friend. The rest of the team is phenomenal, I’ve been impressed by those I recently met, and I’m eager to reunite with former colleagues. 

Great people, great technology… this is going to be fun.