Finish Level 0 (usually a 5-minute aff_a or first_word ) immediately. Get those 50 points. Then, do not touch the hardest problem. Go straight to the medium one. If you finish the medium one (GNL), you have 50 + 100 = 150 points. You pass. You can stop. Anything else is for glory.
Do not memorize code. Know where the \n goes. Respect your static variable. And when you hit ./grademe , take a deep breath. The computer is not judging you; it is just waiting for the right logic.
Good luck. See you in Rank 03.
In the ecosystem of 42, the exams are not just assessments; they are rituals. Unlike traditional tests where you memorize a fact and regurgitate it, a 42 exam drops you into a minimalist shell, disconnects you from the internet (and your dotfiles), and asks a simple, terrifying question: Can you actually build this?
If you are staring down the barrel of , you are no longer a tourist. Rank 00 was about learning to type gcc and making the Norminette happy. Rank 01 was about understanding pointers and memory allocation. Rank 02 is where the filter begins. This is the exam that separates those who watched the videos from those who broke their keyboards debugging.
Rank 02 is designed to make you feel that impostor syndrome one last time before you realize you are actually a developer.
Without the distraction of "optimal solutions" from Google, you are forced to rely on your own logic. If you get stuck, do not stare at the screen. Walk to the bathroom. Get water. Talk to the rubber ducky (the imaginary one, don't get kicked out). The answer is usually a misplaced free() or an off-by-one in your buffer size. Rank 02 is usually the first exam where memory leaks cause an automatic failure. You cannot just "make it work"; it must be clean.
You have written this code before. You just have to write it again, from scratch, without looking.
Finish Level 0 (usually a 5-minute aff_a or first_word ) immediately. Get those 50 points. Then, do not touch the hardest problem. Go straight to the medium one. If you finish the medium one (GNL), you have 50 + 100 = 150 points. You pass. You can stop. Anything else is for glory.
Do not memorize code. Know where the \n goes. Respect your static variable. And when you hit ./grademe , take a deep breath. The computer is not judging you; it is just waiting for the right logic.
Good luck. See you in Rank 03.
In the ecosystem of 42, the exams are not just assessments; they are rituals. Unlike traditional tests where you memorize a fact and regurgitate it, a 42 exam drops you into a minimalist shell, disconnects you from the internet (and your dotfiles), and asks a simple, terrifying question: Can you actually build this?
If you are staring down the barrel of , you are no longer a tourist. Rank 00 was about learning to type gcc and making the Norminette happy. Rank 01 was about understanding pointers and memory allocation. Rank 02 is where the filter begins. This is the exam that separates those who watched the videos from those who broke their keyboards debugging.
Rank 02 is designed to make you feel that impostor syndrome one last time before you realize you are actually a developer.
Without the distraction of "optimal solutions" from Google, you are forced to rely on your own logic. If you get stuck, do not stare at the screen. Walk to the bathroom. Get water. Talk to the rubber ducky (the imaginary one, don't get kicked out). The answer is usually a misplaced free() or an off-by-one in your buffer size. Rank 02 is usually the first exam where memory leaks cause an automatic failure. You cannot just "make it work"; it must be clean.
You have written this code before. You just have to write it again, from scratch, without looking.