Dispatch routing engine
PLACEHOLDER. One sentence for the index card — the problem and the result, no adjectives.
- Python
- FastAPI
- Postgres
- OR-Tools
Outcome
The problem
PLACEHOLDER. Two or three paragraphs on what this was costing the client before you arrived. Be concrete about the before state — how many people, how many hours, what broke when someone was on leave. This section is doing the work of making a reader recognise their own situation, so resist summarising it into a single tidy sentence.
Approach
PLACEHOLDER. What you actually built and why that shape rather than another. Name the constraint that drove the decision — the integration that had to keep working, the data that turned out to be dirtier than expected, the thing you tried first that did not hold.
This body is MDX, so headings, lists, images and code blocks all work:
# A snippet is worth including when it shows a real decision,
# not when it is here to look technical.
Outcome
PLACEHOLDER. What changed, quantified where you have the numbers and described honestly where you do not. The metric tiles above pull from the frontmatter, so do not repeat those figures here — use this space for what the numbers do not capture.