Planning Without the Complexity
April 11, 2021 · David Okafor · 4 min read
The hardest part was not the code but agreeing on how the team should work. Before launch we tested everything on old phones and slow networks. After switching storage layouts, reports are generated several times faster.
Tests do not guarantee the absence of bugs, but they make bugs cheaper. We rely on open formats so the data can be exported at any time. This section collects answers to the questions we hear most often.
Prototyping
The numbers showed that people come back more often when pages load quickly. People rarely read manuals, so hints have to be short and specific. A good layout starts with the text, not with the pictures.
We dropped several external dependencies and never looked back. It helps to agree early on which metrics actually define success. One rule helped a lot: every decision should fit in a single paragraph. Tests do not guarantee the absence of bugs, but they make bugs cheaper.
- Architecture
- Security
- Prototyping
Team Workflow
A short summary first. Every week we pick one problem, dig into it and write down what we learned. Good tools are invisible until the day they break. One rule helped a lot: every decision should fit in a single paragraph. Most of the interface is built from a small set of reusable components.
These pages are updated whenever a new version ships. People rarely read manuals, so hints have to be short and specific. We rely on open formats so the data can be exported at any time.
Thanks to everyone who sent comments and suggestions. Good tools are invisible until the day they break. People rarely read manuals, so hints have to be short and specific. Every week we pick one problem, dig into it and write down what we learned. Moving the build to a dedicated machine made releases much calmer.
pip install troumotas-client
python -m troumotas_client --check