TWIL November 6th 2026
- Ruby has both
raiseandthrow;throwshould always be used with acatchfor non-error control flow- Also I always use
throwuntil someone points it out in review because I've spent too long in JS land
- Also I always use
digdoes not always work to rescuehash[:key][:nested_key]accesses- because the value of
:keycan be a string,digworks by calling itself recursively and strings don't have adigmethod - so instead you need to rescue
NoMethodError, which is obviously much clunkier/bulkier than just callingdig
- because the value of
- Rebasing to incorporate multiple changes from PR feedback might look cleaner, but it's both annoying to mess up and annoying to review
- Tailing logs via the AWS CLI times out after a while
- but if you happen to have spun up an ECS container for the task you were running, you can just go look at it in the AWS console
- We have a lot more users in staging than prod, at least with potentially invalid attributes (> 200 000 vs 68 000)
Links
- How the heck do touchscreens work - Shri Khalpada
I still remember how slow and janky my first touschscreen phone felt. Always assumed it was just software/prcoessing improvements which solved that but it's interesting to learn the touchscreen hardware also played a large part.
Rakhim points out that despite tech companies constantly tracking us and collecting as much information about us as possible, none of it actually results in any of the useful benefits you might expect from such data collection.