Performance: Where to Start
August 22, 2022 · Samuel Price · 3 min read
The project moves in small steps, and that is its main strength. A good layout starts with the text, not with the pictures. The project grew over the year, but the principles stayed the same. These pages are updated whenever a new version ships. We started with a small prototype and slowly turned it into a working product. After switching storage layouts, reports are generated several times faster.
We started with a small prototype and slowly turned it into a working product. The most useful ideas came from people who use the product every day. Moving the build to a dedicated machine made releases much calmer. Good tools are invisible until the day they break.
Configuration details are covered in the following sections. It turned out that half of the time went into agreeing on small details. Every change is rolled out to a small group of users first. These pages are updated whenever a new version ships. People rarely read manuals, so hints have to be short and specific. Thanks to everyone who sent comments and suggestions.
The project grew over the year, but the principles stayed the same. Before launch we tested everything on old phones and slow networks. The hardest part was not the code but agreeing on how the team should work.
Accessibility
The hardest part was not the code but agreeing on how the team should work. It turned out that half of the time went into agreeing on small details. Most of the interface is built from a small set of reusable components. These pages are updated whenever a new version ships.
We dropped several external dependencies and never looked back. The easiest way to start is to copy an example and adapt it. Moving the build to a dedicated machine made releases much calmer. We started with a small prototype and slowly turned it into a working product. Sometimes the best fix is removing something instead of adding a feature.
docker run --rm -p 8080:8080 troumotas/app:latest

Working With Data
Here is the story in order. A good layout starts with the text, not with the pictures. Tests do not guarantee the absence of bugs, but they make bugs cheaper. We keep a changelog so it is always clear what changed and when. People rarely read manuals, so hints have to be short and specific.
This section collects answers to the questions we hear most often. We try to write code that will still be easy to read a year from now. The hardest part was not the code but agreeing on how the team should work. A good layout starts with the text, not with the pictures. Most of the interface is built from a small set of reusable components. Every week we pick one problem, dig into it and write down what we learned.
pip install troumotas-client
python -m troumotas_client --check
- Mobile Layouts
- Planning
- Working With Data
- Infrastructure
- Build Pipelines
- Prototyping