<aside> 💡

We have aligned together on our engineering principles as an agreement on how we want to work together. They are specific to how we make certain decisions at Kombo and apply in addition to general software engineering practices.

</aside>

💎 Quality • Long-Term Velocity

We build for long-term speed by keeping our quality bar high. We choose the right balance between moving fast today and protecting future velocity. We use AI to accelerate our work without lowering standards.

Do’s

• We bias toward action for reversible decisions, and we slow down for one-way doors
• We invest in test coverage, sound API design, observability, and security by default
• We fix root causes, not just symptoms
• We treat AI output as a draft and review it like any other code

Don’ts

• We ship without QA, without tests, or without understanding failure modes
• We over-engineer too early or add complexity that does not pay off
• We let AI generate “slop” or tests that do not reflect real scenarios

🎯 Ownership • Own the Outcome

We own our work end-to-end. Our work is done when it runs reliably in production and creates value for customers, not when the PR is merged.

Do’s

• We take responsibility for rollout, adoption, and ongoing maintenance
• We proactively seek feedback, educate others, and close the loop
• We monitor what we ship and respond quickly when things break