bitboop

Thanks for pointing this out! Would you mind elaborating on your experience?

Would it be feasible to do some "intelligent" TTL updates? By which I mean, don't let the cached data expire automatically. Instead, query a service that informs it of any outage on the backend. If an outage exists, the TTL is renewed. Otherwise, the TTL is expired.

For the `F5` spammers, they would be served with the stale data, until the backend recovers from the outage.

I'm sure I've missed some obvious reason why this isn't a good idea. I'd love to know why.

Personally, I'd rather not immediately jump into building the next thing. After having worked on any significant project, I find writing documentation helpful on a selfish level: I use it to wind down and let my brain idle for a while. I don't think it's a good thing to go full tilt from building one thing to the next. It's good to pause in between, appreciate what's been accomplished, reflect on lessons learned, and take a well deserved break. I find writing documentation an excellent vehicle for that.

I appreciate the feedback, thanks for listening :)

I mostly make acoustic music, but I've been dabbling with electronic music. My first electronic track with vocals: https://youtu.be/zjo0ElTSsuQ