today I'm thinking about how floating point numbers can be treacherous -- what are specific examples of when they've betrayed you?
so far I have:
* money calculations where you need to get the exact correct answer * twitter's tweet IDs are bigger than 2^53 and can't be represented as a Javascript number, you have to use a string * implementing numerical algorithms (like matrix multiplication) (I've never done this)
tiny holiday project: I made a little site to show/hide boosts for the people you follow on Mastodon, using the Mastodon API https://manage-boosts.jvns.ca/
I'm not really taking feature requests but I found it helpful so I'm sharing in case other folks do as well
I know $12 USD is a lot of money for some people, so to celebrate 1000 sales, I'm giving away 1000 copies of The Pocket Guide to Debugging (honour system: please only use the free link if you can't afford $12!)
I'm wondering if there are more tips I should include here -- for example "remove the parts specific to your program when Googling the error" feel too obvious to me
really enjoyed reading this interactive guide to flexbox, I learned some new things about flexbox (like how it interacts with `min-width` which has confused me many times in the past)