On the last week of 2014 we silently released 10 new features that, as all of our features does, aim to improve software developers productivity through increasing visibility and traceability across software construction processes.
Every new feature and improvement that we constantly deliver to the community, has the intention to empower individuals with useful information about their behavior. We strongly believe that such information improves teams’ interactions through data-driven decision making processes.
These 10 new features emphasize our mission of delivering innovative, trustworthy, and accurate metrics that increase transparency and show developers and teams their achievements while gaining insights and traceability of their work without effort thanks to automatic time, activities and artifacts tracking.
So, what about those ten new features?
Well… we’ve released features that goes from having a hint of the busyness for a developer, to handling your and your teams’ data using online pivot tables for the sake of gaining more and more visibility. But, we believe, that the new feature that shines and opens a whole new path for Codealike is the ability to track web browsing and debugging on Chrome.
Let us introduce each feature below:
Tracking Web Activity
Based on the feedback from some of our users that use to code web applications and their UI, we’ve implemented a Chrome Extension that allows developers to track the time spent on each website as well as the time used on debugging the code of the UI using Chrome Devtools.
Users of this Chrome Extension can also track and visualize this information without the need of signing-in to Codealike. Regarding activities tracked, users can also choose to track Navigation time, Debugging time or Debugger time (time spent exclusively on DevTools panel when detached from tab).
Web Activity report and Web Activity presence in other reports
Since we track all this activity as we already track activity on IDEs, that means we track at millisecond precision, that generates tons of information that you can exploit and see across all Codealike’s reports.
For unlocking this feature, you should install the Codealike Time Tracker Extension and sign-in by using your private token.
Reducing conflicts on teams
One of the most difficult things for a developer to communicate to their teams and managers is the impact of poor design and coding decisions. Sometimes you need to hurry things up, but the trade off is usually related to impacts on software performance and/or code maintainability.
We use heuristics that infers the effort that a particular piece of code demands from developers while interacting with it. It gives you fast visual feedback and hints on code that might be a bottleneck.
We use heuristics that infers the effort that a particular piece of code (Method, Class, Namespace, File, Project or Solution/Workspace) demands from developers while interacting with it. That’s a huge advance for what Codealike can bring to your teams. Because it gives you fast visual feedback and hints on code that might be a bottleneck to you, your team, or someone on your team. That means that, if a piece of code is easy to interact with to a developer, but hard to assimilate to another team member, you can see it (Premium users only).
Your manager asks you to fix a bug on a piece of code you’ve never seen, and don’t know who to ask…
You’ve downloaded that very useful and promising open source project, but have some doubts on decisions taken on a Method and don’t know who to ask…
Have you ever been there?
This new feature shows the history of each contributor that interacts with the code. That means, that you can see who (inside or outside your team) interacted with your code without the need to check commits that represents only a portion of the whole interactions history.
Again, you can see this for a Method, Class, Namespace, File, Project or Solution/Workspace and also see how much time each contributor spent on the code and the machine he or she interacted from.
Reducing interruptions (Experiment)
If you already you don’t know it: We’ve created Codealike not only for visibility and traceability purposes. In the deep of our hearts, we HATE interruptions. We aim to kill interruptions and their impact on productivity. We’ll show no mercy and will do anything that we can to show, prevent and finally avoid interruptions. Interruptions are already damaging not only your patience, but your business and industry.
Say hello to my little friend…
As you might know, Premium users can enjoy our Focus Level feature. This feature allows quantification and visualization of the levels of concentration and interruptions a developer has across coding sessions. Well… what if we can tell your teammates when you’re on a coding streak so they can know that before interrupting you?
Well… what if we can tell your teammates when you’re on a coding streak so they can know that before interrupting you?
We’ve done that in the form of a status flag that’s visible across all Codealike, you can see that flag on the Ranking view, on the Facts view, everywhere.
But we’ve also created a couple of views that might be particularly useful under different conditions.
May I Interrupt?
Let’s suppose you’ve that very kind and polite teammate that interrupts you constantly and you don’t know how to tell him you’re busy, really focused on saving the world through coding. Even though we’ve a feature that allows you to see and show interruptions, now you can prevent interruptions before they happen.
Do you want to quickly see if you can or cannot to interrupt a colleague? No problem, we’ve created a view that you can let visible on your display at the office and see at a glance if a teammate is very focused so you can prevent interruptions.
Fully exploiting your data
Pivot Table (Premium)
Heavy-users of Codealike are intensively using our reports and converting the information we provide into insight for improving their own work as well as their teams’ work. We need to empower those users with the ability to exploit their and their teams’ information the way they want. So now our users can use this online pivot table to answer questions like:
- From which machine does my team spent more time building this solution?
- What method demanded more time debugging for a given Project?
- How many hours did our team spent on debugging a particular method on last june and july ?
- How many minutes did I spend reading a file from the computer at my house?
Well… you know how to figure out your own questions, we’ll provide the answers.
Changes to Premium features
Ranking goes public
We’ve received some feedback from our users and we’ve found that the Ranking is a valuable feature not only for Premium users, but also for other users and non-Codealike users. So we’ve decided to show current and past week Top 100 ranking to everyone. Enjoy and spread the voice, there’s nothing wrong in showing-off a little.
Members’ reports (Premium)
This is huge! Now you can see all the activity from all your colleagues altogether. That means that, by choosing this option, you will see the evolution of the indicators for all the activity related to developers and solutions in a team, not only yours or a single dev, but EVERYONE AT YOUR TEAM.
You can activate this just by checking the option after you select a team at each report view.
Bonus track: Gravatar support
We hope you enjoy these new features. Please, remember that we need your feedback on a daily basis 🙂
For getting in touch with us, you can access our Feedback Portal and send us your suggestions and messages.
Finally, help us to spread the voice about Codealike. Tweet, post, share, and if you have a blog or an online community, we’ve something for your readers.