My 42 Journey

how i got here

before 42, i had written maybe a hundred lines of C. i knew what a variable was, what a loop looked like, and that was about it.

the 42 way

42 doesn't have teachers. no lectures, no slides, no graded assignments. you're given a project specification and left to figure it out. the first few weeks are brutal — you're learning to code while also learning how to learn without a guide.

what changed

after my first project, something clicked. i stopped thinking about syntax and started thinking about systems. how does memory work? how does the OS schedule processes? what happens when you press enter in a terminal?

key takeaways

• persistence matters more than talent — the people who succeed at 42 are the ones who don't give up
• teach to learn — explaining concepts to others is the fastest way to understand them
• building from scratch — implementing something yourself gives you knowledge no tutorial can