Process
How We Work
We are a consulting company that writes software. This is how we do it.
Saeloun is not a product company. We do not have one codebase that we polish for years. We work on multiple client projects, each with different stacks, teams, and constraints. That means our process has to be adaptable, but our standards do not change.
Every project gets the same quality bar: clean code, tested features, clear communication, and honest timelines.
Rhythm
Daily Rhythm
We do daily standups. Keep them short. Say what you did, what you are doing, and what is blocking you. If it takes more than 2 minutes, it is not a standup, it is a meeting.
Outside of standups, work asynchronously. Write things down. Do not schedule a meeting when a Slack message will do. Do not send a Slack message when a pull request description will do.
Shipping
How We Ship
Ship small. Ship often. A pull request should do one thing. If your PR description needs bullet points to explain everything it does, it is too big.
Feature branches should live for days, not weeks. If a branch has been open for a week, something is wrong. Either the scope is too big, you are blocked and not saying so, or you are polishing instead of shipping.
Every PR gets a review. Not a glance and an approval. A real review where someone reads the code, checks the tests, and pushes back if something is not right.
Tracking
Time Tracking
We track time because we are a consulting company. Clients pay for our time, and we owe them honest accounting.
Log your hours in Miru daily. Not at the end of the week from memory. Daily. It takes 30 seconds and it keeps everyone honest.
Standards
The Non-Negotiables
- Every feature has tests.
- Every PR gets reviewed by someone who did not write it.
- Every commit message says what changed and why.
- Every deploy is someone's responsibility, not nobody's.
- If something breaks in production, you fix it now. Not tomorrow.
These are not aspirational. These are the minimum.