Skip to content
Barmaj

Mentorship and code review

The part you cannot get anywhere else: an experienced engineer reading your actual work and telling you what they think.

The part you cannot get anywhere else: an experienced engineer reading your actual work and telling you what they think.
#128 · feature/retry-timeoutAdd retry to the payment client
Illustration of review style
  • Blocking

    What happens if the provider times out here? Right now the caller gets a resolved promise and no data, which is indistinguishable from an empty result.

  • Suggestion

    The retry logic and the parsing are doing two jobs in one function. Splitting them would let you test the retry without a fixture.

  • Nit

    Naming — `data2` will not mean anything to you in six months.

First response within one business day. Every comment says whether it blocks.

Mentorship & code review

Senior attention on your actual work

This is the part you cannot get from a tutorial, a course, or an AI assistant that agrees with you. Someone experienced reads what you wrote and tells you what they think.

Code review
Line by line, on every pull request, with the reasoning attached.
Architecture feedback
Whether your design fits the system or fights it.
Engineering feedback
How you work, not only what you produced.
Decision guidance
How experienced engineers choose between two reasonable options.

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
Mentorship and code review · Barmaj