Request IDs Are Useful When They Survive the Whole Journey
A request ID in one log line is useful.
wade womersley – york based software engineer
Engineering notes from the sharp end
wade womersley – york based software engineer I write the way I work: direct, useful, and more interested in what holds up in production than what sounds clever on a slide.
303 published posts
Latest update
Latest post
A request ID in one log line is useful.
Archive
One of my favourite things about furry conventions is how quickly the wonderfully ridiculous starts to look normal.
A temporary feature flag is very good at becoming a permanent piece of the application.
A test that repeats the implementation can pass while proving very little.
My favourite sort of Halloween decoration is the one that has wandered slightly away from being scary.
“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.
A database migration can work perfectly on your development machine and still make a production deployment awkward.
Putting the washing away could use a boss-battle soundtrack.
Pagination looks simple until the underlying list changes between requests.