Team and Roles

Team and Roles

Team

• @canquesse — Maintainer
• @Simurg41 — Maintainer

Both maintainers work across the whole stack. Who takes which task is decided by the two of you, per issue — this page does not pre-assign anyone.

Core principle: learn the same thing, do different things

This project has two goals, and both matter equally:

1. Product — ship an actually-used open-source tool
2. Competence — get both people to the same profile (AI Platform Engineer)

The second goal conflicts with a classic division of labor. If you say "you do Java, I'll do Python", by the end of the month you have two half engineers. So the rule is:

Learning is not divided. Implementation is divided.

That is: every month both people learn the same concept list. But that month's coding work is split between you (you decide how). The part you don't implement yourself, you close by reviewing your partner's code and by the mid-month teaching session.

Three mechanisms

1. Rotation (mid-month)

Whatever areas you split at the start of the month, swap them in the second half. That way nobody gets locked into one language or one part of the stack. The point isn't who starts where — it's that by month end each of you has touched both sides.

2. Mandatory cross-review

You cannot merge your own code yourself. Every PR is read and approved by the other person.

Review is not for fixing lines, it's for understanding. Rule: if you can't explain a PR as if you wrote it yourself, don't approve it. Ask about what you don't understand — asking questions is the real job of review.

3. Teaching session (around the 15th of each month, 60–90 min)

Each person picks half of that month's concepts and explains them to the other at a whiteboard, without notes. A concept you can't explain counts as not learned and is repeated until the end of the month.

Decision-making

Decision type	How
Daily technical choice	Whoever is doing it decides
Affects the service contract	Both must approve + ADR
New dependency / technology	Both must approve
Roadmap change	Both must approve
Disagreement	Run a small experiment, measure, look at the data. If inconclusive, pick the reversible option.

Expected effort

12–15 hours per week per person:

What	Time
Learning (reading, video, experimenting)	4–5 hours
Writing code	6–7 hours
Review + pairing + meetings	2–3 hours