These icons, when showed for an artifact, represent that that particular piece of code exceeded any of two thresholds that we define based on the proportion and amount of time Reading, Editing, Coding or Debugging the code.

In other words: we’re using some heuristics to determine what piece of code is hard to understand, and hard to manage from a programmers’ standpoint.

How much time consuming is to deal with poorly-crafted code? Where are the bottlenecks in the code?

In other words: we’re using some heuristics to determine what piece of code is hard to understand, and hard to manage from a programmers’ standpoint.

So, basically, next time you’ve some time for refactoring code and don’t know where to start from, you can choose your candidate by doing this:

If you don’t see any, you can change two things to go deeper on your search:

The period of time you’re evaluating.

The people using the code. You can do this by filtering for a team and then checking: “Show activity from all colleagues”.

TIP: Simplify your visualization by clicking on this buttons to quickly filter elements that may require your attention.

2 – How is John (Or any other developer :-)) dealing with the code? Does he need help? (Premium feature)

So, imagine that your teammates are coding day and night and you would like to know where you can help. Easy-peasy-lemon-squeezy.

If you have a Codealiike Premium account, then you can see your teammates’ reports. Go to your dashboard and on Colleagues Ranking widget, expand the menu for the teammate you would like to analyze and select Code Tree report.

Refine the period you’d like to analyze.

Filter by using this buttons:

What do you think about this feature. Will it help you find pieces of code that needs your attention?