The dependencies in a CI workflow deserve the same attention as the packages in the application it builds.
Category: Programming
A permission request makes more sense when the user has just chosen the feature that needs it.
Moving a failed message to a dead-letter queue can keep a worker from repeatedly tripping over the same problem.
Catching every exception around a coroutine can accidentally turn cancellation into an ordinary application failure.
An HTTP 304 response is supposed to arrive without a response body.
Checking whether a record exists before inserting another one does not guarantee uniqueness.
A webhook can contain perfectly sensible JSON and still fail signature verification.
A request ID in one log line is useful.
“Run it at six” is incomplete information for a scheduled job.
Replacing app.js and hoping every cache forgets the old version is a fairly unpleasant deployment strategy.