Learning to program is not the same as becoming an engineer. A curriculum can provide projects, concepts, deadlines, and an environment in which people learn — but the depth at which someone understands a problem, the quality of the solution they produce, their ability to reason about systems, and their willingness to go beyond what is required are shaped by the environment around them.
ARGC exists to build that environment.
The Problem
A curriculum's minimum passing standard is a floor, not a target. When the environment treats that floor as sufficient, people learn to reach it. Projects get completed without being understood. Concepts get used without being questioned. Certificates get collected without the underlying ability changing.
This is not a criticism of 42, of any school, or of any student. A curriculum is designed to be achievable by as many people as possible, and it succeeds at that. What a curriculum cannot do is demand more than it was built to demand.
What ARGC Wants Instead
ARGC does not want members to simply learn technologies, complete assignments, collect certificates, or reproduce solutions that already exist. It wants to create an environment where people:
- develop deep technical ability rather than familiarity;
- understand the systems behind the technology they use;
- build things that hold up under someone else's scrutiny;
- investigate difficult problems that have no obvious answer;
- apply what they learn to unfamiliar contexts; and
- eventually contribute original engineering and research work.
The Question
ARGC does not compete with the 42 Amman curriculum and does not replace it. Members continue their normal 42 journey. What ARGC adds is a second standard, held deliberately above the first:
What happens when we refuse to stop at the minimum?
The answer to that question is the entire purpose of this organization.