Objectives
The results that you must achieve in the program, and why discipline counts as much as technical skill.
Upload the maximum quantity of solutions to the challenges that have no
solution in the repository. Fluid Attacks calls each of these solutions a
Unique Solution1.
Philosophy says that Fluid Attacks values discipline as much as technical skill, or more. Thus, do not stop when your first solution takes much more time than you thought.
Knowledge
You upload solutions. But the goal is to learn a new thing. The knowledge has a value in each phase, and the value is not the same:
- In
journeyandquest, what you learn also gets you a job at Fluid Attacks. - In
onboardingandpractice, what you learn calibrates and improves your technical level.
When you know one area of Fluid Attacks Academy well, you must find new challenges. This is your duty in all the phases.
Footnotes
-
A challenge gives no unique solution for two reasons. A talent solved it first, in the repository. Or nobody solved it, and its
OTHERS.lstfile holds a link. The second reason belongs to hacking.So read
OTHERS.lstbefore you start a hacking challenge. One line in that file, and the challenge gives you no unique solution.You can still upload a solution to such a challenge. It teaches you GitLab and the repository. It adds nothing to your unique solutions.
The
Pending challengescolumn of Site ranking counts the challenges where a unique solution waits.A ctf-hacking solution of such a challenge counts for the exit criterion of your stage. It is not a unique solution, and it does not change your metrics. Terms gives this rule. ↩