Mastering 42

less pain, more gain. An opinionated strategy guide on how to get the most out of 42.

Welcome, welcome, dear fellow travellers through the universe of 42 :)

#Whom is this guide for?

For anyone who wants to learn more while doing the 42 curriculum.
This guide aims to take away some things that may hinder you throughout the curriculum, while also providing some kind of general map for the terrain.

Note, however, that it aims to be a benevolent guide for your own long-term learning. It might discuss stuff you do not need right know to solve the task at hand. Instead, it tries to show you what other ways you might walk in order to achieve that.

#Why?

Because the Curriculum right now is putting stones in your way. All the time. I am not sure whether this happened by accident or on purpose (and it should 'encourage' you to ask your peers). What I am sure about, however, is that it hinders learning and slows you down. This time with your peers surely is better spent on discussing different approaches on how to solve a project, rather than on figuring out what the hell the project wants you to do.

#Purpose & Goals

This is written for the ones who want to learn more than the bare minimum needed to complete the projects.
We'd like to provide:

  • A map of the terrain around to each project, and of the paths from one to another.
  • A good mindset to learn things.
  • A comprehensive additional resource for each project.
  • General advice, thoughts and ideas on doing stuff at 42, programming-related and non-programming-related.

Found something to improve? Edit this page on Github!

The Holy Graph →