CodeLogic, a Continuous Software Intelligence (CSI) company, aims to help developers understand the software they are developing and make changes without breaking the code. Developers are working with very complex software and they can be apprehensive to make changes to it for fear of breaking it. The company’s platform uses graph database technology to scan the binaries of post-compiled files and see what is happening with the application when it is running, so they can see all the dependencies.

In this episode of TFiR Let’s Talk, Swapnil Bhartiya sits down with Brian Pierce, CEO of CodeLogic, to discuss the challenges developers are facing with complex software and why there is a need to understand the software structure to avoid the break/fix cycle. He takes a deep dive into their CSI platform and how it is helping developers reduce software breaking code and better identify potential vulnerabilities.

Key highlights from this video interview are:

• CodeLogic’s CSI platform aims to help developers be more productive by helping them understand what their software structure is and make changes without having to break it. Pierce goes into detail about their platform and how it helps developers to see the dependencies.
• CSI involves profiling binaries at runtime, as well as, working inside the IDE plugin to see where all the dependencies are before making a change so that you can see what might break in the structure of the code. Pierce explains how the platform fits into the wider CI/CD and DevOps space.
• CodeLogic is primarily targeting developers and development teams dealing with Java code, .NET, and SQL databases. A lot of legacy code is written in Java and .NET, but many are trying to cloudify the application; however, Pierce explains that this can be challenging unless you understand the structure of the entire application.
• Pierce discusses how CodeLogic is helping tackle technical debt by illuminating potential problems and helping developers not to break code. He goes into depth about the other use cases that stem from this such as ramping developers, documenting code, and keeping it documented.
• While CodeLogic is not a cybersecurity tool, it does help developers remediate cybersecurity issues. Pierce explains how when the Log4J security vulnerability became known last year, their tool helped developers scan and find all the classes that had Log4j, so that it could be remediated quickly. He also elaborates on how it can help with REST endpoints.
• According to Pierce, a recent poll in a Developer Focus site showed that the number one issue with developers was not feeling productive enough, followed by work-life balance. He goes into detail about the challenges developers are facing and how the break/fix cycle can hold up projects and cause problems, explaining how CodeLogic can help solve this challenge.
• CodeLogic does not have any direct competitors; however, there are tools available to use to find and put together the graphical structure of an application. Pierce explains how other available tools work and why CodeLogic’s capabilities to continuously analyze the dependencies of the code in application differentiates them from other tools.
• CodeLogic’s platform is available for download as a free trial, and people can go straight into the sandbox and use the application itself as well.

Connect with Brian Pierce (LinkedIn)
Learn more about CodeLogic (Twitter)

The summary of the show is written by Emily Nicholls.