It's not a bad argument to try to understand an existing system before changing it.
I've seen a lot of "why is this like this? I'm changing it" blow up in software. The clearest memory was not realizing that user names could be null, even though that looked impossible by tracing the registration route. Turns out there was another, stupider, way of registering.
It's especially a good argument when the person evaluating the system has no domain knowledge or expertise.
I think one of the reasons some of the little kids in my life like me is I try to give them honest explanations. They don't always fully understand, but I think they appreciate getting answers. And probably appreciate the occasional "I don't know, actually. Let's look it up"
What is an example of a safety rule who’s conditions no longer exist which would not have the conditions almost immediately return if the rule was removed?
My job is populated by dinosaurs that only recently adopted git for version control. They had some rules and procedures that made a kind of sense when deployment meant "I'll scp the files to the prod server", but don't add value anymore.
Some people had a rule where after "deploy" they would SSH into prod and check the md5 hash of the files and compare them to their local copy. You don't have to do that.
They also wanted to only allow one person to work on a file at the same time because "you can overwrite their changes". Git handles that fine (unless you really fuck up the merge conflict, admittedly)
Sometimes the real reason is uncomfortable and they don't want to say it out loud. Like, "the CEO is an idiot, and wants it this way for stupid reasons"
Though maybe "the CEO doesn't understand how Google calendar works, so he thinks putting our time off in a shared spreadsheet is easier" would satisfy?
At my job a lot of stupid things come out of "someone high ranking doesn't understand computers" or "they don't benefit from fixing this, so it's easier for them to leave it stupid"
I find teams won't mark messages as read. Like I'll be focused on the chat and it'll stay unread. I have to click out and back into it.
When there's one of those horrible "teams" things with threads, clicking on a new message on the sidebar shows me just that message. No context. I have to click on the channel and find it.
The core problem is they have "chats" and then some other horrible thing that looks like channels but sucks. Maybe they wanted that to be like a message board? I hate it.
Most of my work uses "chats" instead, but that's horrible. No discoverability. A thousand permutations of people in chats. One for every meeting. (Was that important message in the standup chat? The planning chat? The side chat with the three competent guys?). And no threads.
If Sony was selling a backlog going back to 1980 at deep discount with no monthly fees and DRM-free at the seller's discretion, they would get less flak.
I think they have incentives to tag broadly but not accurately so they pick up more visitors. Tag it as "anal" when there's like a glimpse of butt, and you might get more views from people looking for that. There's no mechanism to punish inaccurate titles and tagging that I know of.
I'm pretty sure they don't invest in search because it's a poor return on investment. Most people just hit the first page, crank one out, and leave. The next cohort is similarly easily satisfied with their crap search. The people looking for specifics like "big tit short red hair reverse cowgirl pov outdoors at dusk" aren't profitable enough to spend engineering time on.
Wasn't there a famous guy who beat up like 50 Nazis during WW2? The judge was like "are these all the victims?" And the prosecutor said "the rest are in the hospital?"
Despite civic ignorance, overwhelming majorities are grateful (86%) and proud (79%) to be Americans. Most also believe America is a land of opportunity (61%), and even more believe the American Dream (74%) is available to them personally.
Consoles haven't seemed worth the price since like... the PS2 era, maybe PS3.
I might have a little more tolerance for jank than some people, though. Some people are like "I had to go into the settings and change something" like it's a dozen years hard labor.
There's an element of self control to sticking to values. I've seen people proclaim like they're going to boycott EA because of various reasons, but then some shiny new game comes out and those values fall.
Maybe they never really had he values in the first place.
It's not a bad argument to try to understand an existing system before changing it.
I've seen a lot of "why is this like this? I'm changing it" blow up in software. The clearest memory was not realizing that user names could be null, even though that looked impossible by tracing the registration route. Turns out there was another, stupider, way of registering.
It's especially a good argument when the person evaluating the system has no domain knowledge or expertise.