Five Lessons on Architecture
October 20, 2022 · Samuel Price · 10 min read
This note sums up a few months of work. Sometimes the best fix is removing something instead of adding a feature. After switching storage layouts, reports are generated several times faster. The numbers showed that people come back more often when pages load quickly.
It helps to agree early on which metrics actually define success. Good tools are invisible until the day they break. A good layout starts with the text, not with the pictures. Nothing here is a solo effort: a small team works on the project. After switching storage layouts, reports are generated several times faster.
Infrastructure
Some processes are automated, but key decisions are still made by hand. Before launch we tested everything on old phones and slow networks. We started with a small prototype and slowly turned it into a working product. Good documentation saves more time than any optimization. Moving the build to a dedicated machine made releases much calmer. Every week we pick one problem, dig into it and write down what we learned.
One rule helped a lot: every decision should fit in a single paragraph. It helps to agree early on which metrics actually define success. Good tools are invisible until the day they break. We try to write code that will still be easy to read a year from now. Sometimes the best fix is removing something instead of adding a feature.
docker run --rm -p 8080:8080 troumotas/app:latest