Hacker News Reader

Comment by ___alt | Hacker News Reader

> Yes, they modelled it after Epita which was also about code, code, code.

I don't know where you last got your information about Epita, but this has been less and less true for around 10 years now.

They sought to have a state certified engineering degree for a long time and implemented a lot of changes around 2003-2007 that made the cursus a bit less about code a more about common engineering stuff (maths, physics, english, ...) with more structure (they structured classes with a credit system, made more standard student evaluations, ...)

Source: graduated in that era, been in touch with later students.

View on HN

Coming from Epitech, I would say that you are right. The code, code, code mind is more Epitech and less Epita nowadays.

I've also been through Epitech which is the school that greatly inspired 42 (same founders) and I would like to add some details on top of that.

Even if it's true that Epitech us mainly about coding, the program enforce a coding standard that is a huge part of the final grade of each coding project (small functions, 80 char per line of code...). Fom the second year, components decoupling and basic design patterns are part of the program.

Nevertheless, the school doesn't really make the most to teach basic good engineering practices or at least I don't remember (doc, tests, vendoring, observability...) and this is one of the main pain point.

They have the same rules at 42 to code, 80 columns, 25 lines for a function, ect... Where Epitech is better is that from the middle of the third until the end of the beginning of the five year, you have to work on a end study project. You need to prepare everything before coding, database schema, how will you do your tests, ect.. Even tough I find Epitech better than 42 on this, Epitech is also lacking a lot of things. Some teachers to explain to you the best practices, code review, ect.. would be really nice.

Are you really talking about the EIP?

Reply on news.ycombinator.com