These are the principles ARGC uses to make decisions — how members are evaluated, how work is judged, and how disagreement is handled. They are operating instructions, not decoration.
1. Resilience
We do not define ability by how quickly someone succeeds. We value the ability to remain engaged with difficult problems, learn from failure, recover from mistakes, and continue improving.
Difficulty is part of the process, not a reason to lower the standard.
In practice: a member who fails, understands why they failed, and returns to the problem stronger has done exactly what this value asks for. A member who avoids difficulty has not.
2. Engineering Integrity
We value understanding over appearances. Members are expected to know what they build, understand the decisions they make, and be honest about what they do and do not understand.
We do not reward pretending. We reward genuine competence.
In practice: an honest "I don't know, here is what I do know" is a stronger signal than a confident answer that was guessed.
3. Excellence
ARGC does not define excellence as perfection. Excellence means refusing to treat the minimum acceptable result as the final destination.
Members are expected to continuously ask:
Can this be understood better? Can this be designed better? Can this be tested better? Can I understand this more deeply?
In practice: passing is a floor, not a finish line. Work that meets the requirement but no longer satisfies the person who wrote it is unfinished.
4. Give Back
Knowledge becomes more valuable when it is transferred. Every member is both a learner and a contributor.
Helping another member understand a difficult concept, reviewing someone's work honestly, documenting knowledge, sharing an insight, or creating an opportunity for others are all forms of contribution.
The growth of one member should strengthen the people around them.
In practice: contribution is measured by what it changes for someone else, not by the time spent producing it.
5. Ownership
ARGC members are expected to take responsibility for their own development and their contribution to the community. Ownership means not waiting for someone to tell you what to learn, what to improve, or what needs to be fixed.
When you identify a problem, you are encouraged to understand it and help solve it.
In practice: raising an issue you could have resolved yourself is the beginning of ownership, not evidence against you.
6. Curiosity
We value people who ask why. Technical growth requires going beneath the surface, questioning assumptions, exploring unfamiliar ideas, and being willing to enter areas where the answer is not immediately known.
Curiosity is one of the foundations of engineering depth.
In practice: "why does it work this way" is an expected question, and answering it for someone else counts as contribution.
7. Humility
Technical ability does not eliminate the need to learn. Members are expected to be comfortable saying:
"I don't know."
The important part is what happens next. We seek understanding rather than status, and improvement rather than recognition.
In practice: the strongest technical opinion in the room is the one that survives being questioned.