CodeScene Blog
codescene.com · Company blog · on HN since 2009
CodeScene's company blog, by Adam Tornhill's team, on code quality, technical debt, and mining Git history for risk areas.
What HN saysHN commenters mention CodeScene's hotspot and knowledge-island analysis of Git repos, though one notes the author's company and asks for more detail.
21HN people shared it
10linked it in comments
30stories submitted
115story points
5 months agolast shared
2009people per year2026
Most-shared posts
- 1Homepage5 people · first shared 2021
- 2Measuring Code Complexity by Its Shape and Distribution3 people · 23 points · first shared 2022 · 3 comments on HN
- 3The Business Costs of Technical Debt [pdf]3 people · 6 points · first shared 2021 · discussion on HN
- 4Code quality: measuring the business impact of unhealthy code2 people · 21 points · first shared 2022 · 13 comments on HN
- 5Advancing the state of AI automated code improvements [pdf]2 people · 5 points · first shared 2024 · 1 comments on HN
- 6Why Adding More People Makes a Late Software Project Even Later2 people · 3 points · first shared 2023 · discussion on HN
- 7The technical interview rethought: Evaluating what matters1 people · 8 points · first shared 2022 · 1 comments on HN
- 8Benchmark Study SonarQube vs. CodeScene: CodeScene 6 times more accurate1 people · 6 points · first shared 2024 · 3 comments on HN
- 9Refactoring recommendations – building your own refactoring catalog1 people · 5 points · first shared 2022 · 2 comments on HN
- 10Refactoring components in React with custom hooks1 people · 4 points · first shared 2022 · discussion on HN
- 11What can software developers learn from offender profiling?1 people · 4 points · first shared 2022 · discussion on HN
- 12Sneak-Peek: IDE Integration for CodeScene – code health feedback in real-time1 people · 4 points · first shared 2023 · discussion on HN
- 13How is technical debt related to progress?1 people · 3 points · first shared 2022 · discussion on HN
- 14Refactoring Speeds Development by 43% – From Tech Debt to Triumph1 people · 3 points · first shared 2024 · discussion on HN
- 15First Prize for Best Paper on Technical – Intl. Conference on Technical Debt1 people · 3 points · first shared 2024 · discussion on HN
What HN people wrote when they linked it
nephrenka · 2021-08-06
That's a great visual presentation, but not really an innovation. The CodeScene tool has that built in together with a set of deep analyses on top (see https://codescene.com/).
There are several public conference talks that cover this visualization and related use cases: https://www.youtube.com/watch?v=fl4aZ2KXBsQ
bunsenhoneydew · 2024-11-12
This is one of the features of https://codescene.com/
It looks for knowledge islands and relates those to frequently modified code, to identify hotspot, or areas of high risk due to low knowledge distribution in areas of high change.
Another use is if someone hands in their notice you can easily see all the code that only they know, so your handover planning is mapped out easily.
I’ve never thought of it being used maliciously, it’s for visibility. It would be a shitty manager that would use it that way and if they’re already shitty then this tool won’t change that.
nickcox · 2023-01-29
There's also Adam Tornhill's [0] Codescene. [1]
[0] https://www.amazon.com/Books-Adam-Tornhill/s?rh=n%3A283155%2Cp_27%3AAd…
[1] https://codescene.com/
kelsolaar · 2022-10-29
Author’s company is https://codescene.com/, curious to understand what it exactly does, there is no plethora of details on the website.
mjul · 2022-02-03
This is one of the key concepts in how Codescene analyses a code base by mining the Git repo.
It is quite useful to find find problem areas and tacit knowledge such as “when you change this API these two client side adapters should probably also be updated”
See https://codescene.com/
empis · 2022-03-17
Disclaimer: I work at CodeScene.
Here's a link to some docs about how code health is calculated: https://codescene.io/docs/guides/technical/code-health.html
In simple terms we try to measure cognitive complexity of source code.
A more in-depth description of one of the factors:
https://codescene.com/blog/bumpy-road-code-complexity-in-context/
pron · 2021-08-06
That's the same visualisation used by CodeScene (https://codescene.com/how-it-works/), but there is a more elaborate one that represents affinity (number of connections) as distance to create something like a geographical map: https://homepages.ecs.vuw.ac.nz/~craig/publications/vissoft2015-hawes.…
yreg · 2020-11-23
Are you sure it couldn't be installed locally?
My client is a bank with private GitHub servers, so I assume their codescene is self hosted as well.
edit: Yep, there is an on-premise option: https://codescene.com/pricing/
harpastum · 2009-10-07
I didn't even realize any browsers still had the go button. That's one 'feature' that has never existed in safari. Here's a screenshot of safari 1.2, circa 2003:
http://www.codescene.com/browsercam/Mac-Safari1.2.jpg
richardw · 2024-12-17
"You seem to confuse"
"Your analogy with the automakers seems puzzlingly irrelevant"
"Your take is rather romantic."
That's pretty charged language focused on the person not the argument, so if you're surprised why I'm annoyed, start there.
Meta has one: https://arxiv.org/abs/2410.08806
Another, edited in above: https://www.linkedin.com/pulse/multi-repo-ai-assisted-refactoring-unlo…
Another: https://codescene.com/product/ai-coding
However, I still don't recognise the names. The one I saw had no pricing but had worked with some big names.
Edit: WAIT found the one I was thinking of: https://www.youtube.com/watch?v=Ve-akpov78Q - company is https://about.grit.io
In an enterprise setting, I'm the one hitting the brakes on using LLM's. There are huge risks to attaching them to e.g. customer-facing outputs. In a startup setting, full speed ahead. Match the opinion to the needs, keep two opposing thoughts in mind, etc.