.tips
page 3 of 10, 228 small things in all. back to the first.
.july
2026, 17 tips.
The kill switch is not the rollout flag
reliabilityfeature-flags
Snapshots for output you would diff by eye, nothing else
testing
Mock HTTP at the network, not the function that calls it
testing
Pin GitHub Actions by commit digest, not tag
securityci
Tests that touch time use a fake clock
testing
Publish with OIDC and delete the npm token
securitynpmci
A test name is the sentence that is true when it passes
testing
An error budget turns 'is it reliable enough' into a number
observabilitysre
Do not install a package published this week
securitynpm
If the fix is 'wait', it should not page
observabilitysre
One dashboard per service, four panels at the top
observabilitysre
Turn off install scripts and allow the few that need them
securitynpm
Sample the boring logs, keep every failure
observabilitycost
pytest -x --lf when you are fixing a failure
pythontesting
Pick field names once and use them everywhere
observability
Four log levels, with a rule for each
observability
uv replaces pip, venv and pip-tools in one binary
pythontooling
.june
2026, 8 tips.
Put deploys on the graphs
observabilityoperations
A barrier makes race conditions reproducible
pythontestingconcurrency
A cron job that stops running is silent, so give it a heartbeat
observabilityoperations
Declare the PR's scope, and let CI enforce it
code-reviewci
p99, not the average
observabilityperformance
One request id, on every log line, across every service
observability
Read the code first, then the tests, as claims
code-reviewtesting
Every alert carries the link to its runbook
observabilitysre