Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
33 reviews
from
External reviews are not included in the AWS star rating for the product.
Great tool for statistical analytics
What do you like best about the product?
Helps teams plan goals to improve their codehealth and identify knowledge gaps. It is easy to use and integrate with github repositories.
What do you dislike about the product?
It does not yet support all languages for analysis.
What problems is the product solving and how is that benefiting you?
Planning goals to improve codehealth across our repositories
Using PR integration CodeScene helps us to react to issues quickly
What do you like best about the product?
PR integration and quick feedback as part of build process
What do you dislike about the product?
Applying same expectation to test files and test set up with regards to how long the tests are or duplicate code which is sometimes inevitable. However, I understand you can define rules around this to have better control.
What problems is the product solving and how is that benefiting you?
Early feedback and quick signal if code quality drops or improves
Good way to make sure PRs are good to be merged
What do you like best about the product?
Makes reviewing PRs easier as you can see if the code health has declined.
What do you dislike about the product?
Tests can affect the score with duplication which is acceptable in tests, but it can be customized.
What problems is the product solving and how is that benefiting you?
I can see where the code has declined with the VSC extension
CodeScene is a static analysis tool, It a helps development teams by serving as a quality code.
What do you like best about the product?
CodeScene is a static analysis tool, It helps development teams by serving as a quality code and an early feedback loop before merging the code. Latest new features are very nice
What do you dislike about the product?
There is not much, they are improving day by day.
What problems is the product solving and how is that benefiting you?
Static code analysis is valuable in finding code that is overly complex, bumpy roads, quality score, and overall code complexity. Also new changes are very helpful to make our code perfect.
A transformative revelation in-regards to program analysis.
What do you like best about the product?
The data mining of data analytics (including historical trends) combined with the GitLab integration provides regular and consistent recommendations for improving code quality.
What do you dislike about the product?
There is a lack of a robust ROI model that demonstrates reduced defects and time in development.
What problems is the product solving and how is that benefiting you?
Code quality and ensuring that any remediations are high-value. Any technical debt re-work is done on high-value and high-impacting parts of the codebase.
Static code analysis and UI with a suite of stats and graphs - great for tracking project health.
What do you like best about the product?
CodeScene is good at picking up code smells and the VSCode extension makes it really easy to use and pick up code smells before they make it to version control. CodeScene offer a UI that provides a whole host of stats and metrics on our code, such as commit frequencies, knowledge distribution, code health scores along with which files are problematic and why, all of this makes it really simple to go in and improve our code. CodeScene is straightforward to get started with and offers version control PR integration where it can let us know if the code health is decreasing and how/where.
What do you dislike about the product?
Some of the rules set by CodeScene seem arbitrary and unnecessary, I know these can be customised to our needs but often code is dynamic. We have some APIs that are wrappers for a database or whatever which often get flagged by CodeScene but in reality, this API is probably fine for what it is. There are other examples for some of the rules CodeScene sets such as primitive obsession. Sure, you could maybe argue this is a wider problem but arbitrarily grouping primitive parameters into objects to increase our code health score doesn't feel correct. Lastly, a minor point about the UI, I would say the learning curve is somewhat steep. There are a lot of tabs, metrics and graphs which can be a bit overwhelming to navigate at first.
What problems is the product solving and how is that benefiting you?
CodeScene helps make our projects better. More maintainable by checking the knowledge distribution. Easier to pick up for new developers by looking at code smells and static code analysis like anti-patterns in code. CodeScene tracks all this and more, and packages it into a suite of products (VSCode extension, web UI, CLI tool etc.) that help aid development and overall project health.
CodeScene: Enhancing Code Quality and Developer Productivity
What do you like best about the product?
It is good for comprehensive analytics to improve code quality which allows quick feedback. Tool is easy to use which makes it good for new and experieced users to utilise. There are a number of features provided, e.g code health monitoring, hotspot anaylsis and knowledge distribution.
What do you dislike about the product?
The configuration and setup at the start is slightly hard to do for larger projects and complex codebases. It does not currently support all languages for metrics and anaylsis.
What problems is the product solving and how is that benefiting you?
It is good for comprehensive analytics to improve code quality which allows quick feedback and it provides better communication between technical and non-technical users.
CodeScene is a great tool
What do you like best about the product?
The CodeScene application provides a great insight into Code Health as well as things such as Technical Debt, Development Time and Knowledge distribution across the team.
What do you dislike about the product?
The UI can sometimes be a bit tricky to navigate with some features feeling quite hidden in sub tabs
What problems is the product solving and how is that benefiting you?
CodeScene is providing insight into our applications and highlight where improvements should be made to improve quality of the code, both in maintainability and readability
Brilliant Product Complements Other Analysis Tools
What do you like best about the product?
Easy to use, you just set up your projects and leave it. Every time you commit your code, an analysis is done and code-smells, problems, etc are reported. You can then interactively analyse the suggestions.
What do you dislike about the product?
Not really a problem but it highlights how bad my code really is :)
What problems is the product solving and how is that benefiting you?
My poor implementation of SOLID principles.
Unearthing technical debt, identifying lost knowledge and enabling non-tech stakeholders empathy
What do you like best about the product?
On an organisation level, the data we've gathered helps our teams move forward in a better way by having additional information and signals to facilitate delivery.
From an engineering perspective, we can help identify team productivity bottlenecks and areas most expensive to maintain, support onboarding with knowledge maps of a system or domain, assist with off boarding by identifying the areas in need of knowledge transfer, help to maintain standards and more.
CodeScene can be deployed into a continuous integration pipeline and can integrate with a git repository to automatically analyse pull requests and identify high-risk commits. The analysis can help engineers who are less experienced with the code base review high impact code changes and catch potential problems before they are delivered to the main branch of the code base.
Identifying delivery risks before they become an issue if also a beneficial signal from a product engineering team perspective. A possible scenario involves a project that involves understanding and adapting an area which contains a lot of hotspots and complex code for a team built of mostly new engineers. Using these tools allows better visibility, questions and delivery estimates.
Having this real world information up-front from an onboarding perspective for a EM, HoE, VP and CTO role is also something not to be quickly dismissed.
We not only want to identify our technical debt, but help prioritise what should be fixed and track this over time. Or from a different angle, identify what we don't need to focus on fixing and instead accept our technical debt as the impact is low, therefore the value is likely low.
From an engineering perspective, we can help identify team productivity bottlenecks and areas most expensive to maintain, support onboarding with knowledge maps of a system or domain, assist with off boarding by identifying the areas in need of knowledge transfer, help to maintain standards and more.
CodeScene can be deployed into a continuous integration pipeline and can integrate with a git repository to automatically analyse pull requests and identify high-risk commits. The analysis can help engineers who are less experienced with the code base review high impact code changes and catch potential problems before they are delivered to the main branch of the code base.
Identifying delivery risks before they become an issue if also a beneficial signal from a product engineering team perspective. A possible scenario involves a project that involves understanding and adapting an area which contains a lot of hotspots and complex code for a team built of mostly new engineers. Using these tools allows better visibility, questions and delivery estimates.
Having this real world information up-front from an onboarding perspective for a EM, HoE, VP and CTO role is also something not to be quickly dismissed.
We not only want to identify our technical debt, but help prioritise what should be fixed and track this over time. Or from a different angle, identify what we don't need to focus on fixing and instead accept our technical debt as the impact is low, therefore the value is likely low.
What do you dislike about the product?
The interfaces can be a bit clunky at times, there is a level of onboarding needed in terms of where everything is and sadly, it does not integrate with our ticketing tool for delivery reporting (Linear). All quite minor things though.
What problems is the product solving and how is that benefiting you?
Code hotspots are now visible and represented well, knowledge islands and lost knowledge are visible and can be addressed with kowledge distribution, data on how teams interact with each other is useful, metrics on our team experience levels over time helps set expectations for delivery and being able to set real world refactoringh targets is great in terms of measurement.
showing 11 - 20