So what's the problem? Handling any kind of payment dispute should be part of regular operations. So, when your payment provider has a complaint, handle it, instead of running to Twitter/HN for validation.
Not sure how easy self-hosting those are, but any paid-for and/or online offering by a third party is useless. This should have been clear long ago, but the LastPass breach should have made it obvious.
I know I COULD, but my PO is telling me that they saw this on a really popular website and that we should really be doing it that way because the big guys obviously know what's right.
Unless you investigate this, and keep investigating it continuously, you can't know what information they are exfiltrating from your system intentionally or unintentionally. "Shaping the product" should not require this kind of behavior.
Putting animated GIFs into your documentation or blog articles, negatively impacts legibility. The constant movement diverts attention and makes people skip that section so they can just scroll the annoyance out of view. If you MUST include animated guidance for whatever reason, use videos that have playback controls and are paused by default.
Seeing this in an article on how to improve documentation makes me question any message you might try to get across.
While Macromedia/Adobe Flash was an important IDE for some time, we later developed complex Flash applications in code-centric IDEs (like Flashdevelop) and compiled using the SWF SDK from Adobe. This also came at no cost, as far as I remember.
If you're reimplementing DNS lookups with caching in your own code, you are very likely doing something wrong.
The title of the entire story already had me confused, as it suggests you somehow need DNS for UDP. Everything that is presented here is a caching strategy.