Field note · October 20, 2024
Reader question — Orchestration, and what "it runs every night" costs
The moment analysis becomes a scheduled job, a whole category of problems arrives: dependencies, retries, alerting, and someone's phone at 3am.
Reader question on Orchestration, and what "it runs every night" costs, and the answer belongs somewhere more findable than an email.
The moment analysis becomes a scheduled job, a whole category of problems arrives: dependencies, retries, alerting, and someone's phone at 3am.
The question was, roughly, "when does this stop applying?" — which is the right question and the one lessons routinely fail to answer. Every technique has a range of validity, and stating it is what separates a lesson from a recipe.
It sits in the Shipping it and keeping it alive module. The exercise is a thinking one rather than a query one — some of this material is about deciding what to compute, and that does not need a keyboard.
Ordering matters here more than in most courses. It follows Communicating a result to someone who will not read your notebook and leads into Monitoring data, not just jobs, and reading it out of sequence mostly works but costs you the setup.
Free means free, and it also means we can rewrite it whenever it is wrong. No edition, no errata PDF, nothing to repurchase. The whole course is 36 lessons and the fixes land the day we find them.