What is our primary use case?
We use the product to get an understanding of hotspots, code health, and team dynamics. It helps us understand which section of the codebase is under active development and changing more often than others. This is very informative and helps narrow down the focus to a smaller part of the code base. We have been using this product on-premises on various projects and get insights that are not there in any other tool we have looked at so far.
We have the ability to generate reports, use API keys, and integrate this into pull requests with Git or Azure DevOps and get it into our CI/CD pipeline for continuous monitoring.
How has it helped my organization?
CodeScene helps us understand the evolution of the codebase and identifies hotspots that help to focus on action planning and not worry about every issue in the codebase. This makes it easy to focus on areas that will give immediate benefits.
If we need to roll out, there are changes in the team composition, or we have an attrition case, CodeScene allows us to understand who is doing what instead of relying on just a statement from an architect or project manager. This data-driven methodology is what sets it apart. The simulation that is available is another great way to plan future action plans.
What is most valuable?
The three main aspects we like are:
1. Hotspots: This is the core of the product and helps us to focus on the smaller and most impactful areas of the codebase.
2. Code Health and Code Complexity: This helps us understand the issues and what we need to fix and how. CodeScene provides a summary of the method and function level and helps focus on a smaller section of the files instead of looking at everything all at once.
3. Knowledge Map: This helps us understand team dynamics such as how developers have worked on the code and how fragmented the code is. There's information around knowledge loss and knowledge islands that is very informative.
What needs improvement?
Wild card search options across different sections would be very helpful. For example, having the ability to find all those files which have a knowledge loss of 100% and have a code health score of one could be very useful.
The generated reports could be improved further.
The ability to do an open-source vulnerability check (SCA) would be also helpful since SCA also relies on a static codebase.
Some of the views could drill down between each other so that we could move from one view to another and be able to link the information provided.
For how long have I used the solution?
I've used the product for more than 18 months.
What do I think about the scalability of the solution?
The scalability is excellent. There are no issues when using this on large code bases.
How are customer service and support?
They offer excellent support.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I didn't use another solution.
How was the initial setup?
The initial setup was easy. This is a Docker-based setup on-prem and a cloud version is also available.
What about the implementation team?
We implemented this product in-house.
What's my experience with pricing, setup cost, and licensing?
The setup is very easy. It has both a Docker option and a standalone option for on-premises or a SaaS cloud option. Licensing costs are reasonable given the functionalities.
Which other solutions did I evaluate?
I didn't look at other options.
Which deployment model are you using for this solution?
On-premises
