The 42 path

Step 1

The base of every C project that follows, so it goes alone and first.

• Libft

Step 1In parallel

Both are C and reuse libft while it is fresh, so run them side by side.

• ft_printf
• get_next_line

Step 2

No code, only system administration: a change of pace once the C pair is done.

• Born2beroot

Step 1

It tests the C from M1, which fades first: sit it while ft_printf and get_next_line are fresh.

• Exam Rank 02Exam

Step 2

More C right after the exam, with the examshell habits still warm.

• push_swap

Step 3In parallel

A-Maze-ing is a pair project in Python: find your partner early and build it alongside the modules that teach what it needs.

Step 1

It tests the Python from M2, which fades first: sit it before moving on.

• Exam Rank 03Exam

Step 2In parallel

Both are Python, so do them while the modules and the exam are fresh.

• Fly-in
• Call Me Maybe

Step 3

The only C project of the milestone and independent of the others: leave it for last.

Step 1

It tests what you learned in M3: sit it first, while Python and algorithms are fresh.

• Exam Rank 04Exam

Step 2In parallel

Pac-Man is long and Python; NetPractice needs no code, so it fits in parallel.

• Pac-Man
• NetPractice

Step 3

Step 1

The last exam tests M4: sit it first, before the final project.

• Exam Rank 05Exam

Step 2In parallel

Both are code-heavy and independent, and the exam is still fresh.

• Agent Smith
• The Answer Protocol

Step 3

Step 1

A team project: gather the group first and plan the modules together.

• ft_transcendenceGroup project