Terms

1. Schedule. You can start your training day at any time. Fluid Attacks recommends 8:30 am, because the Peer-Reviewers and the Continuous Integrators start work near that hour. Then you get quick feedback and help with your problems. This hour is a reference, and not a rule.

   Send each solution and each question when it is complete, at any hour of the day. Rules gives this instruction, and it has more weight than the reference hour. A solution that you send at night gets its answer on the next day.

2. Equipment. Install Time Doctor on the laptop that you use for the Academy, and select the task F/ Entrenar - Academy. An employee of Fluid Attacks uses the corporate laptop and the company VPN. A talent in journey or in quest installs Time Doctor on a personal laptop.

3. Progress report. Send a standard progress report before 11:00 pm of each training day. Send it even when you made no merge request (MR) that day. If you sent an MR that day, put it in your report. Use the Daily progress tracker. Select Academy in the Team field, and give these details:

   Nickname: https://academy.fluidattacks.com/users/<your-user>/
   Target: <Team> (The team the talent will join after completing Academy, e.g., "Engineering", "Pentesting")
   Stage: <Current phase> (The talent's current Academy phase. Must match the latest `type` entry in your `users/<assigned-nickname>.yml`)
   Effort: X hours (Total time you have registered in Time Doctor under the F/ Entrenar - Academy task since you started in Academy. Decimal format without rounding, e.g., 48.5 or 67.91)
   Duration: X calendar days (Value from the "Days" column for your user at https://academy.fluidattacks.com/active-users/)
   Workload: X% (Value from the "Workload" column for your user at https://academy.fluidattacks.com/active-users/)
   Success: Y total unique solutions / Z total MR attempts = % (Use Y as an integer from https://academy.fluidattacks.com/active-users/, and Z as an integer accumulated over all time)
   Time to first merged solution: T hours (Decimal format, same style as Total time. Calculate the wall-clock time from the `start` timestamp in your `users/<assigned-nickname>.yml` to the merge time of your first merged solution. Exclude any periods when you were not logged in Time Doctor under "F/ Entrenar - Academy".)
   
   Created issues (only include those from the day of the report):
   
   - url 1
   - url 2
   
   Merged MRs (only include those from the day of the report):
   
   - url mr 1
   - url mr 2

NOTE: Do not put the guidance text in parentheses in your final report.

4. Dedication. Fluid Attacks evaluates your daily dedication against a reference time. The dedication field in your users/<assigned-nickname>.yml file gives your reference. The Workload criterion below gives the hours of each value.
5. Time tracking. Use the time-tracking tool all the time that you give to Fluid Attacks Academy. In Time Doctor (TD), select the option F/ Entrenar - Academy. In the Daily Progress Tracker, set the Team field to Academy. If you have a question about these tools, ask your recruiter immediately.

CAUTION: Time Doctor records only the one task F/ Entrenar - Academy. It does not divide the time between the challenges. Therefore the hours that it shows increase while you work on other challenges on the same day. The effort value in each solution YAML must be your correct estimate of the time for that specific challenge.

If a reviewer closes an MR for corrections, and you continue the work, add the extra time to effort. You cannot open a closed MR again. Correct the errors and send your work in a new MR, and give it the effort of both attempts. Commit and merge request gives this rule.

Your merged solutions carry a sum of effort. That sum must stay in a margin of 5% of your Time Doctor total under F/ Entrenar - Academy. The margin is the reason for the absorption rule. That rule puts the hours of an attempt that does not merge into your next merged solution. Uniqueness gives the procedure.

Exit criteria

Fluid Attacks considers a talent for the completion of a stage only when the talent meets all these conditions:

• Solving time above 50 h.
• Acceptance rate (MRs and questions) above the threshold of the stage:
  • 1st academy stage: above 70%.
  • 2nd academy stage: above 75%.
  • 3rd academy stage: above 80%.
• Workload above 95%. Fluid Attacks computes the workload against 42 h/week for a full-time talent, or 21 h/week for a part-time talent. Fluid Attacks removes the Colombian public holidays and the justified absences from the days denominator. Therefore these days do not decrease the metric. The users/<assigned-nickname>.yml file records the justified absences.

NOTE: The Workload criterion is not applicable to a talent in the journey phase. All the exit criteria are not applicable to the quest phase, which Fluid Attacks evaluates in a different way. For more information, read How it works.

The focus is quality and speed, and not the quantity of time. The time increases only when a talent is not productive, or gives too few hours, or sends incorrect solutions.

Academy stage is one process that you did in the Academy. Your stage number is the quantity of entries in the periods list of your user file. A talent who returns for a new process gets a new entry. The acceptance threshold then increases. The Stage: field of the progress report is a different thing. It names your current phase.

Solving time is the sum of the effort of your merged solutions. From that sum, Fluid Attacks removes the effort of your first merged solution. That effort is the time that you used for it.

Acceptance rate is (merged MRs + approved questions) / (total MRs + total questions). A question is a failed question when the documentation already gives the answer. Such a question has an answer that is a direct link to the documentation. The threshold increases with each academy stage. Fluid Attacks expects fewer rejected submissions and fewer repeated questions from a talent who returns.