How do you separate the good from the bad? What do you do when Microsoft changes the good things into bad things?
My take is that Microsoft consistently makes bad things and makes "good" things into "bad" things; so, I don't have much expectation or faith that anything that I currently think is "good" will stay that way.
What blows my mind is how short sighted it is. Even the oligarchs benefit from scientific research. Even the oligarchs lose money when our industries move to other countries.
Onirim is good but the phone app is better since there’s so much shuffling. Cursed?! is one of my favorites. Galdors Grip is really cool in that you can play it in hand, you don’t need a table, so you can play it anywhere.
Since you brought it up, I personally switched to jujutsu and prefer it greatly. I regularly help coworkers deal with issues in git and keep dropping hints like `in jujutsu this would've been done way easier like this!`. Nobody bites yet since I think most of them don't want to use the CLI but maybe someday if enough people keep talking about it the inertia will get to the point that we can get some really slick GUIs for jj.
Basketball is also the problem, refereeing specifically. Refs are humans and make mistakes but it’s hard to watch and not feel like there’s blatant favoritism to star players or certain teams.
There are the L2M reports that detail all the mistakes they make in the end of the game and way too often they’re game altering.
Then there’s the inconsistent approach to the rules. They’ll suddenly decide they want to push a rule, call every tiny infraction on it, then 10 games later it’s like the refs collectively forgot the rule exists at all.
It all makes for an extremely frustrating experience for the players and the fans.
IME hard disagree. Projects with any longevity and/or turnover will have code that doesn’t seem to make sense but was put there for a reason. Commit messages are key to giving the context because even though there might be descriptions people will put the relevant slack messages and jira tickets in the pr or commit.
At this point I almost weekly have to review the full context on a pr to make sure my fix won’t break some historical use case that isn’t immediately obvious.