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.
I switched to using masked emails with Fastmail primarily so I could see who sold my data. The potential security benefit was not really a driver. Having 1Password be able to generate a unique email makes it a no-brainer these days. For those services that require a username that is not your email, they can usually be used without the domain part. Works really well.
I even wrote a tiny little local only web app that I can use to generate a masked email on my phone, so when I need an email for an in person thing I can just show them my brand new weird email directly on my phone.
Not really any places where things get sold, but opt-in in the background for newsletters is bad in certain sectors. Ticket platforms are terrible. I like to use a new email for every event and boy does that lead to new round of clicking opt-out until I can deactivate the email after the event has concluded.
Basically the same as cleaning up after they hired the cheapest dev they can find. Something our little shop has been doing for 4 years now. Can't wait to charge to debug a 100,000 line vibe coded WordPress plugin.
Not sure, I use dnsimple for dns and wrote my own little service to update my A record, no ip6 in my corner of the world so have not checked for AAAA record support.
This looks nice, I like how many of these tools have been surfacing. I recently started using https://readeck.org/, which aims to solve some of the same problems and really like it. Much better than a "bookmark" tool for things like articles.
My two favorite parts of Readeck are:
- it provides a OPDS catalog of your saved content so you can very easily read things on your e-book reader of choice. I use KOReader on a Kindle and have really enjoyed reading my saved articles in the backyard after work.
- you can generate a share link. I have used this to share some articles behind paywalls with friends and family where before I was copying and pasting content into an email.
I am currently maintaining and adding to a React app started in 2016. React is fine. 9 years of decisions by numerous people that are no longer working on it, and I can still improve and update it. I can even bring in developers with no experience on the code base to change things. I would change 75% of it now, but that is not a React problem, that is a normal development problem.
React is fine, it is stable, standard, and still works for almost any use cases. There are not many JS libraries that have stood that test of time.
I’ve noticed an increase in small distilleries creating their own versions of Malört over the past five or so years. It reminds me of the renaissance Fernet experienced 7 or 8 years ago. Malört is definitely an acquired taste—taking a shot of it feels like punishment—but if you enjoy bitter liquors, sipping some chilled Malört after a heavy meal might not be unpleasant.
I’d guess that bitterness is the flavor most people are least interested in exploring, and that makes sense. It doesn’t seem to have the same endorphin payoff as other tastes. It’s an interesting flavor, and I think you need to have an interest in digging into unusual flavors before diving into the world of bitter-forward spirits. I think it makes sense that the rise of better cocktails has led to spirits like Malört seeing growth.
Besk has existed for a long time in Chicago, which I've heard referred to as "good Malort." It has a brighter, anise-forward flavor which puts it more in line with Italian amari.
Most of the alternative, new Fernets I've tried want to be "Branca, but more approachable", which takes away a lot of what makes Branca so interesting. I don't know if "Malort, but less bitter" is as marketable.
Amaro is fairly sweet. Malort is closer to Jagermesiter, but with a much more bitter flavor. I'd look into Becherovka if you want something a little more "zesty"
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.