logo

Academy

DocumentationThe program

Metrics

The metrics that Fluid Attacks measures — dedication, unique solutions, average hour per unique solution and initial commits — and where to see yours.

Fluid Attacks keeps this process as objective as possible. To do this, Fluid Attacks measures a set of variables. These variables let Fluid Attacks make objective job offers, and they let your team leader follow your progress.

The general ranking shows the metrics of most of the talents who entered Fluid Attacks Academy. Select a user to see more metrics. Most of the metrics have a clear name and a help bubble. A metric is a technical matter. Make a question work item (issue) to ask about one. Rules gives the channels.

If you are an active talent, use the active users page. It shows your metrics and the metrics of the other talents in the process.

This page shows only your own metrics:

https://academy.fluidattacks.com/users/<assigned-nickname>/

Replace <assigned-nickname> with the alias that the Academy team gives you. First commit gives the alias and the file that carries it.

Dedication

Fluid Attacks must measure your hourly dedication to the process correctly. Fluid Attacks pays1 you for each hour that you record in Time Doctor, even when you upload no solution.

The internal name of this metric is total-hours. Fluid Attacks computes it as Σ effort. This is the sum of the effort value of each challenge. The sum covers all the solutions that you merge into master. Each solution gives only the hours that you used for that challenge.

Therefore you can open more than one merge request at the same time, and the sum stays correct. Only you and Fluid Attacks can see the total value, and this value is not public.

Fluid Attacks measures your dedication with Time Doctor. You must record all the time that you give to the process. Examples of this time:

  • The time when you read the documentation.
  • The time when you install software.
  • The time when you learn commands.
  • The time when you look at videos that help you to solve a challenge.
  • The time when you solve challenges.
  • The time when you make the changes to upload a challenge.

CAUTION: Time Doctor must record all the tasks that a solution needs. Do not stop it during those tasks and start it again only for the upload. Time Doctor must record all the time that you give to the process.

If you are a part-time talent (user.dedication: part-time, 21 h/week), Fluid Attacks expects less time from you. But Fluid Attacks recommends that you organize your time and give a minimum of 3 hours each day. Fluid Attacks computes total-hours in the same way. Terms is the source of these hours.

Unique Solutions

A unique solution is a solution that you upload in a language that has no internal solution and no external solution. Uniqueness gives the two types of solution and the rules of the metric.

Average Hour Per Unique Solution

This metric is one of the most important. It shows the quantity of time that you use to upload a unique solution. Thus it shows how quickly you learn something new. It is the ratio total-hours/unique solutions, where total-hours is the Σ effort sum above. A lower number is better.

NOTE: Do not try to lower this metric at all costs. Fluid Attacks recommends that you work at your own speed. Fluid Attacks looks at the direction of the number in the middle term: the number must become lower with time.

Initial Commits

This metric shows the quantity of attempts that you made before your first correct solution. It shows your resilience and your tolerance to frustration. Fluid Attacks does not look for a specific number. Fluid Attacks looks at the change in the number with time.

Footnotes

  1. This is applicable if you are in journey, where Fluid Attacks pays you for each hour that Time Doctor logs. Fluid Attacks pays a talent in quest 200 USD for 6 challenges in 2 weeks, and not for each hour. Fluid Attacks pays a talent in onboarding or practice through the employment contract. For more information, read How it works.

On this page