Knowledge base
This knowledge base is maintained by our consultants and is an embodiment of how we work, our tools and processes.
How this section is organised
Section titled “How this section is organised”Each article is short, opinionated and dated, so it stays useful rather than turning into a wiki nobody trusts.
Categories. Every article sits in a category. There are four categories; tools, techniques, frameworks and platforms.
A house view, not a rule book. Where an article recommends a practice or a tool, it carries one of three statuses:
- Default is what we reach for unless there is a reason not to.
- Consider is a fair choice in the right situation, with eyes open.
- Caution is something we usually avoid, and the article says why.
This lets us have an opinion without pretending there is only ever one answer. The client’s context always wins over the amarti default.
Freshness. Every article names when a person last reviewed it. A page past its review is still usable, but treat it with a pinch of salt and flag it so it gets looked at.
The shape of an article
Section titled “The shape of an article”Keeping a consistent shape makes articles quick to write and quicker to scan. A new one covers, roughly in this order:
- What it is in a sentence or two.
- When to use it, and when not to.
- How we do it here, kept concrete.
- Watch out for the common ways it goes wrong.
Ways of working
Section titled “Ways of working”The delivery and engineering practices we lean on, each written up so a team can pick it up without a workshop: