The fact that this also shuts off access to many public library Ebooks on these devices should be getting more press. My wife exclusively uses her Kindle for library books and it looks like it will be impossible to get legally acquired library books onto her device from our library system, which is using libby/overrdrive.
Track it! Any Spreadsheet. Columns: date, where you filled up, how many gallons, dollar total, odometer reading, mpg function ((currentodo - prevodo) /gallons), ppg function (total / gallons).
You could also install something like https://lubelogger.com/ (naming decision aside), if you happen to do any self-hosting. It is a lightweight vehicle tracker. It has a fuel tracking screen. I personally only use it to track maintenance, but have been thinking about starting to track fuel consumption given the current disruption.
I have been using HA to water my garden for 4 summers. I setup a Tempest weather station this fall, and will have some fun experimenting with using rain and temperature data collected in my back yard to make watering decisions.
The honest answer is you probably won't find it. Historical documentation is hard, it is the first "features" cut when teams are scrambling to meet a deadline. There is no malice in this, it's just something that the end user doesn't need or see so when shit hits the fan, it get skipped.
Commit logs, slack/email/etc, documentation silos, or issue trackers are your best bet, other than actually being able to talk to the author(s) of the code.
But in general, the decision was made because in the time the developer had to implement the feature or fix, this was the best solution they could come up with. Hopefully if there were clear tradeoffs, there is some comment as to what they might have done with more time. Likely though they were rushed, told their team they wanted to go back and fix this, and then were ushered into a new project the second this one stabilized.
I think gghhjnuhbb has the best alternative to finding actual documentation and that is sitting and putting yourself in their headspace. That can sometimes lead to insights you might have missed.
This is why I hate the common pushback against "TODO:" comments. They're an extremely fast way to leave a trail of what alternative path would have been taken had there been more time. They're part of the code, so they don't get caught up in a "backlog grooming" the way a Jira ticket will, and don't break flow the way switching to Jira will.
Funny, I am taking an American Sign Language course, and one of the components is talking about dates/days/weeks. Next Week, Next Monday, Last Tuesday, etc. I was talking to some of my classmates who were all struggling to fully understand when to use what sign(as was I), and I pointed out that talking about next Friday in English can get confusing depending on how each participant thinks about things.
Not surprised an LLM gets this wrong, lots of content consumed with various ideas on how these things should should work.
