About this handbook
Why the handbook exists, who it's for and how to use it.
This handbook describes how engineering works at AltLabs: how we make decisions, the standards we hold ourselves to, the tools and technologies we build with, and how we deliver for our clients. It's the single source of truth for how our development team operates.
Why we created it
As we've grown, much of how we work has lived in people's heads, in old conversations, and in habits passed on informally. That works when a team is small, but it makes onboarding slower, leads to inconsistent decisions across projects, and leaves knowledge at risk when people move on.
This handbook writes those things down. It captures what already works well, sets clear expectations where things have been unclear, and gives everyone the same foundation to build on.
It also prepares us for how software development is changing. AI is reshaping both how we build software and what we build for clients. Clear, well-maintained documentation helps us adopt AI tools responsibly and helps those tools do better work, because they can follow our conventions only if those conventions are written down.
Who it's for
It's for everyone involved in building software at AltLabs:
- New starters getting up to speed
- Experienced engineers checking how something is done
- Leads making decisions on new projects
- Colleagues outside engineering who want to understand how the team works
It also helps when we collaborate with clients and partners who need to know our standards.
How to use it
Treat it as a reference, not a rulebook to memorise. When you start a project, choose a tool, review code, or handle an incident, the guidance should be here.
Where it explains why we do something, that reasoning matters as much as the rule. Good judgement is still expected, and if you think something here is wrong for a particular situation, raise it.
Search is the fastest way in
Press ⌘ K (or Ctrl K) on any page to search the whole handbook.
A living document
This handbook will never be finished. It's being built in stages and will change as our team, our clients, and the technology change.
Everyone is encouraged to contribute: if something is missing, unclear, or out of date, propose a change. A handbook only stays useful if the people who rely on it keep it accurate.