Readable SQL and readable schedules have the same enemy: systems that only emit one long line. You do not need a perfect pretty-printer to win a code review - you need enough structure that a teammate can spot a missing join, a rogue cartesian product, or a cron field that will fire on Sundays when marketing meant weekdays.
SQL readability: what “good enough” looks like in review
Start by separating major clauses onto their own lines - SELECT, FROM, WHERE, GROUP BY, ORDER BY. Then indent boolean groups so AND/OR precedence reads like the logic tree you meant. If your ORM emits a wall of text, capture the generated SQL, run it through the SQL formatter, and paste the result into the ticket - future you will recognize the join keys faster.
Dialect reality check
Generic formatters do not understand every vendor extension. Window functions, dialect-specific casts, and dollar-quoted function bodies may still look awkward after an automated pass. Treat formatted SQL as a draft you execute in a safe environment - not a substitute for EXPLAIN plans or migration tests.
Cron: the five-field mental model
Classic Unix cron strings have five fields: minute, hour, day-of-month, month, day-of-week. Kubernetes and systemd timers often inherit the same vocabulary with different sharp edges (time zones, suspend/resume, daylight saving). Before you paste a string into production YAML, run it through the cron expression helper to narrate each field - then confirm semantics in the scheduler docs for your platform.
DST and “obvious” schedules
A job that runs at 2:15 every day will behave differently around spring-forward gaps depending on whether the host interprets local time or UTC. Document the zone next to the cron line in your runbook. When correlating actual fires against logs, translate with the Unix timestamp converter so incident timelines line up with UTC log stamps.
SQL formatter vs database “Format document”
| Need | Browser formatter | IDE / database tool |
|---|---|---|
| Quick Slack snippet cleanup | Fast, shareable, no repo checkout | Heavier setup for a one-liner |
| Deep dialect-aware refactors | May need manual touch-ups | Better awareness of vendor grammar |
| Teaching juniors joins | Good enough to show shape | Pair with live query plans |
Regex and JSON companions on the same desk
Cron and SQL debugging often sit next to log grepping. When you are extracting structured fragments from messy lines, test patterns in the regex tester and read the regex beginner guide. When the extracted chunk claims to be JSON, validate with JSON validator before piping into dashboards.
Developer hub
More utilities live on the developer tools hub. If you are bouncing between schedules and auth tokens in the same incident, pair this guide with JWT decode vs verify.