Engineering growth
A record of how you work, built from evidence attached to real pull requests — not a score, not a certificate.
Engineering growth
Your growth, backed by evidence from your actual work
Not a quiz score and not a certificate. Every claim about how you work points at the pull request that shows it, and a mentor can explain it to you in one sentence.
- No leaderboard, and no ranking against other members.
- No commit counts, no lines of code, no pull request totals.
- A level moves only when two different reviewers have seen it.
- You can read the evidence behind every level, and disagree with it.
Growth profile
Illustration — not a real member- TestingStrong
Added failure-path coverage nobody asked for, twice
- Requirement interpretationStrong
Asked what happens on timeout before building
- Code qualityDeveloping
Factoring improved across three consecutive PRs
- ArchitectureDeveloping
Chose the simpler option and wrote down why
- CommunicationConsistent
PR descriptions a reviewer can start from cold
- Response to feedbackStrong
Argued a point on the merits and changed the design
What we will and will not claim
No testimonials yet, because there are no members yet
Barmaj is new. Rather than borrow credibility we have not earned, here is exactly what we commit to — and you can hold us to it.
A human response within one business day
Measured from the moment a pull request is ready for a person, in business hours. When reviewer capacity runs out we pause taking new members rather than let turnaround slip.
Every claim about you is explainable
If a mentor cannot explain a piece of evidence to you in one sentence, it does not get written down.
No ranking members against each other
No leaderboards, no commit counts, no lines of code. Those numbers reward the wrong behaviour and we do not collect them as scores.
Your work stays yours, on your own GitHub
Contributions happen on your account, so what you build is visible and verifiable without taking our word for anything.
When members finish their first projects we will publish what actually happened, including the parts that did not work — with their permission, and anonymised where they ask for it.
You don’t need another tutorial.
You need experience.
Applications are read by a person, and places are limited by how many pull requests we can review properly each week.
Apply to Barmaj