About CodeScene
CodeScene pricing
CodeScene has a free version and offers a free trial. CodeScene paid version starts at €18.00/month.
Alternatives to CodeScene
CodeScene Reviews for UK Users
Feature rating
- Industry: Information Technology & Services
- Company size: 11–50 Employees
- Used Weekly for 1+ year
-
Review Source
Enabled my team to be faster
I really like the Delivery Performance functionalities that allows me to rapidly visualize and act on the most important lead time metrics such as Lead Time for Changes or Planned vs Unplanned work. This insight and the possibility to quickly identify areas in our code with highest technical debt and complexity, areas that leads to quality issues, is a killer feature
Pros
The possibility to connect the history of your code with business metrics that allows you to drive and push for increased speed as this is increasingly more important going forward.
Cons
The user interface could be more intuitive.
- Industry: Civic & Social Organization
- Company size: 51–200 Employees
- Used Weekly for 1+ year
-
Review Source
CodeScene Provides Actionable Insights
CodeScene as a company has been highly responsive to my input over the whole course of my engagement with them. My suggestions based on real-world usage contributed to improvement in the products. Throughout my entire engagement, the CodeScene team has stayed highly engaged to make sure I was getting the most out of the product. Opening the tool for the first time was a truly exciting experience, and the more I learned, the more excited and empowered I got.
Pros
CodeScene gave me a view of the code base in a way that no other tool - or person - could. It helped me understand where our quality issues really came from, and to redirect my team to focus on remediating those areas. This not only improved quality but helped make sure we were focused on the most refactoring value.
Cons
There aren't a lot of downsides to this tool. The subject matter requires a lot of knowledge that takes time to attain. This is to say you have to understand the theory behind the insights to get the most value out of them. However, I'd argue that any engineering manager -should- understand this theory if they want to be effective at managing any code base. It shows up all the meaningful metrics I'd always hoped for and never knew existed.
- Industry: Computer Software
- Company size: 501–1,000 Employees
- Used Weekly for Free Trial
-
Review Source
One of the best code quality controlling software!
CodeScene is one of the best visual tools to identify pull requests that leads to technical debts.
Pros
The most important thing about Codescene is that it allows the software development team to remove technical debts from the source code that can severely impact the performance of the software system later.
Cons
It was indeed quite difficult to remove all the technical debts all at once and when we use this tool our release frequency decreased.
Alternatives Considered
Nexus LifecycleReasons for Choosing CodeScene
Better visualisation and interpretability and economical compared to the $775 Nexus lifecycleSwitched From
Nexus LifecycleReasons for Switching to CodeScene
Less expensive and easy to use.- Industry: Information Services
- Company size: Self Employed
- Used Weekly for 1+ year
-
Review Source
Making the invisible visible
Just recently I had the privilege of doing a formal analysis of the code base of the client using CodeScene. I spent two days analysing the code base of around 35 active developers. The company wanted to see if some of the difficulties they had could be better understood by looking at the code and more importantly by looking at the interaction patterns with the code.
My peers were thrilled at the level of understanding they could acquire in such a short timespan! Not only does it give hope in showing that it's only a small fraction of the technical debt that actually counts, including which part! But it also gives valuable insights into concerns around the code, like team organisation, developer turnover and even product management difficulties.
I've been using CodeScene for more than a year now. I'm a technical coach and as I get to see a lot of different teams. CodeScene really improves my understanding each team's situation and thus I can be of better use to them.
Tools are only tools numbers are only numbers but when a tool is making the invisible visible then it is really, really useful for making more informed decisions!
Pros
Otherwise almost invisible information is pulled up right into our face
The incredible insight it gives into the pain points of the project in a very short time.
That it focuses on only the most costly problems
It's focus is not only code, but also team dynamics, delivery dynamics and architecture.
I don't know of other tools that look at Change Coupling
Very visual
Cons
The UX is sometimes confusing, this is probably where there's most room for improvement.
Alternatives Considered
SonarReasons for Switching to CodeScene
I still use Sonar from time to time. The two tools are complementary. For instance there's no code coverage in CodeScene. If I use CodeScene a lot more than Sonar it's because it points more directly to actual problems. Besides it requires no compilation, no test run, and it has great support for a lot of languages. I even got great information from running it on an unsupported language (VB5) because it still understands the git history.- Industry: Marketing & Advertising
- Company size: 51–200 Employees
- Used Weekly for 2+ years
-
Review Source
New insights into your code and organization
Above all else, I appreciated that CodeScene would provide data to check my instincts about where and when to apply more effort to improve a design. As a developer, CodeScene’s hot spot feature helped me feel more confident (or helped me find another candidate) when I identified an area to improve. As a team manager, the metrics and graphs in CodeScene gave our team a way to monitor progress as we worked on a several week effort to make small, incremental improvements to a tricky area of code.
Pros
CodeScene gave us a new insight into a problematic area of our code - team structure. We identified a hotspot that continued to grow as we added new features. The Team Dynamics views highlighted an issue that kept the hotspot growing; several teams contributed equally to the code - a case of a missing shared mental model and lack of clear stewardship. The information generated by CodeScene helped us create a plan to improve the code and the visuals helped us tell a compelling story to our whole team.
We used CodeScene on new projects to help us come up to speed on a new project quickly. We identified the hotspots to prioritize conversation topics with the original authors as we transitioned the code from one team to another. As we started making changes to the project, I appreciated the GitHub Pull Request integration that provided an extra check to see if we had missed changing some files that had historically changed together and might have caused a bug in production.
Cons
We used the hosted solution (codescene.io) which tended to lag the on-premises version and get the newest features later. We were unable to use some of the delivery-focused features as we used Pivotal Tracker and later Clubhouse, neither of which were supported at the time. The UI was sometimes hard to get a summary of the information we needed, though that has improved with the Hotspots Code Health view.
Related categories
- Source Code Management Software
- Product Lifecycle Management Software
- Business Intelligence Platform
- Continuous Integration Tools
- Product Management Software
- Decision Support Systems
- Static Application Security Testing (SAST) Software
- Application Performance Management Tools
- Data Visualisation Tools
- Business Performance Management Software