Why I'm writing one short post every day

A daily engineering log: what I learn building backend and LLM features in production, written down while it's still fresh.

1 min read

Most of what I learn at work never gets written down. A tricky migration, a test that finally caught the bug, a prompt that made a RAG answer reliable: it’s obvious in the moment and gone a month later.

So I’m starting a daily log here. One post a day, short on purpose.

What to expect

  • Backend design: APIs in FastAPI and NestJS, data modelling in PostgreSQL, and the trade-offs behind them.
  • LLMs in real products: retrieval, evaluation and the boring parts that make a chatbot trustworthy.
  • Delivery: testing with Jest, CI/CD, Docker and Terraform.
  • Working in Germany: notes on building software for public-sector and social projects.

The rules I’m giving myself

  1. Write about something I actually did or read that day.
  2. Keep it under ten minutes to read.
  3. Include code or a concrete example whenever possible.

Some posts will be in German, some in English, depending on the topic. If you want to follow along, there’s an RSS feed.