ulvishukurza.de
  • Writing
  • Guides
  • About
Get in touch
ulvishukurza.de
  • Writing
  • Guides
  • About

Colour mode

Get in touch

The blog

Notes from the lab.
  1. May 12Stop unit-testing your pipelines. Property-test them.
  2. Apr 28What I learned rebuilding attention in one weekend
  3. Mar 30B1 in six months: German grammar that compiles
  4. Feb 17The case for boring orchestration
  5. Dec 08A year of shipping LLMs to production, in numbers
  6. Oct 21Postgres is enough (until it isn't)
  7. Aug 04Reading papers with a notebook, not a highlighter
All notes

Data Engineering

  1. Writing
  2. /
  3. The case for boring orchestration

The case for boring orchestration

Feb 17, 2025 · 7 min read
Data EngineeringFeb 17, 20257 min read

Most pipelines need a scheduler, retries and alerts. They do not need a platform. A plea for cron, a queue and a good runbook.

Written by Ulvi · Bonn, Germany

← A year of shipping LLMs to production, in numbersB1 in six months →

Let's build something that thinks.

ulvi@shukurza.de
  • GitHub
  • LinkedIn
  • RSS

© 2026 Ulvi · Bonn, Germany · Built with Astro

© 2026 Ulvi · Bonn, Germany

  • GitHub
  • LinkedIn
  • RSS