Feb 19 · 8 min read · Purpose of Day 2 The purpose of Day 2 is to move beyond writing scripts that run and start writing scripts that operate systems. In real environments, Bash is commonly used to: Take application backu
Join discussion
Feb 13 · 9 min read · Scenario: A critical backup cron job has silently stopped working 3 days ago. The backup script is located at /opt/backup/backup.sh and should create daily backups in /var/backups/daily/ , but no new backups have been created recently. Looking at the...
Join discussion
Feb 1 · 6 min read · If cron has a single moral lesson, it’s this: time does not guarantee uniqueness. Jobs run twice. Or zero times. Or half a time. Or later than expected. Cron does not promise exactly once execution, and every system that assumes it does eventually pa...
Join discussion
Feb 1 · 6 min read · Cron has a reputation for honesty. You tell it when, it runs then. If something didn’t happen, the instinctive conclusion is: “the code must be broken.” In production, that assumption is often wrong. This article is about the more uncomfortable truth...
Join discussion
Feb 1 · 6 min read · Most systems don’t fail because they picked the wrong database or framework. They fail because they picked the wrong trigger. Something runs too early. Or too late. Or too often. Or only when a user happens to click a button. The code is correct, the...
Join discussion
Jan 26 · 5 min read · Cron jobs are everywhere. They run backups, sync data, generate reports, clean databases, and keep systems alive.Yet some of the most critical cron jobs fail silently, sometimes for weeks, before anyone notices.Here are 10 common cron jobs that silen...
Join discussionJan 25 · 6 min read · By the time a system reaches production, most architectural mistakes don’t announce themselves loudly. They surface as unease. As dashboards that look fine but feel wrong. As bugs that appear only at certain hours. As jobs that “usually” run. This ar...
Join discussion
