HN user
An great counterpoint to this argument comes from Allen Holub in his talk “#NoEstimates”.
The system of making bets does not translate well when communicating that to business folks and managers — which is why it’s largely non-existent for story pointing in agile environments. People are overly optimistic; they hear 80% and think 100%. Doing percentages isn’t foolproof either.
I have been thinking about the same problem as the author, but I’ve reached vastly different conclusions about how to do remote work better.Polar opposite.
I wrote my opinion here: https://www.naveed.dev/posts/consider-xp-for-distributed-tea...
However, I think his points are thought provoking, and it’s interesting to see how someone else thinks about the problem.
I don’t think this blogpost provides any value over the official documentation. You can run through the airflow tutorial in about 30 minutes and understand all the main principles pretty quickly.
Airflow is 100% better at chaining jobs together than cron. The Airflow scheduler makes it so you don’t have to worry about putting “sleep” calls in your bash scripts to wait for some conditions to be met, and allows for non-linear orchestration of jobs. You might have different flows that need to run on different schedules, and with airflow, you can wait until one flow is done before the other starts.