Technical guide
Restore a file to a specific Git revision
Copy a historical file into the working tree or staging area, understand checkout’s overlay behavior, and undo the restoration deliberately.
Technical guide
Fix Cannot find module errors in Node.js
Trace module resolution failures through paths, dependencies, package exports, and deployment output without discarding a working lockfile.
Explainer
Count unique field values in Kibana and Elasticsearch
Use cardinality aggregation for approximate distinct counts, tune precision, and choose a different approach when the count must be exact.
Technical guide
Revert a merge commit that has already been pushed
Choose the correct mainline parent, reverse a shared merge with a new commit, and plan how to reintroduce the feature later.
Technical guide
Undo several Git commits
Reverse selected changes without rewriting shared history, inspect revision ranges, or reset private history while preserving work you still need.
Explainer
Run a cron job as a specific user
Choose a user crontab or a system cron file, and verify the account, environment and permissions used at runtime.
Technical guide
Run shared setup before pytest tests
Use a session fixture for reusable initialization, make its dependency scope explicit, and separate process-local reuse from coordination across parallel workers.
Explainer
Run a cron job on the last day of the month
Use a calendar guard for traditional cron, or a systemd calendar expression that handles month ends directly.
Explainer
Run a cron job once a week
Choose a weekday and time, understand @weekly, and avoid treating week-number parity as a reliable two-week schedule.
Explainer
Run cron jobs every 5, 10, 15 or 30 minutes
Use minute-field steps for clock-aligned schedules, with clear limits for longer intervals and overlapping runs.
Explainer
Run scheduled jobs every 5, 10 or 30 seconds
Choose a timer or a carefully bounded loop for sub-minute work, with explicit overlap and timing behavior.
Explainer
Run scheduled jobs in Go with robfig/cron
Use five-field or second-level cron schedules in Go, control overlapping runs, and handle panics explicitly.