I don’t suppose anything a bit less-serious is available to normies?
I have a iphone that died on vacation and was set to backup only on WiFi (I’ve since changed that setting, haha, whoops) and has a couple days of photos stuck on it that weren’t backed up. It boots and makes noise but the screen is dead. Uncertainty about how broken it is has kept me from paying the not-cheap cost to get a screen replacement, and I haven’t found a way to read its data over a cable without unlocking via the screen first (which doesn’t work, and its touch-sensing capacity also seems to be dead, so blind input doesn’t do it, or else I could probably unlock it with a couple tries and get it to connect to WiFi it already knows and do its backup, but it won’t do that without being unlocked)
It’s probably related to the fact that when they added “await” to JavaScript, it seemed to become the most popular keyword in the language overnight, just comical amounts of it in the average new JavaScript file in the wild.
Quite a lot of my js functions don't await; instead I simply return the promise and let the caller `await` or more often attach a `then` as they see fit.
The default linter in Vs Code keeps marking those functions with warnings though. Says I should mark them as async
I think the core error is marrying a communication tool for the people doing the work, to a reporting tool for people who aren’t doing the work.
Managers are all about that kind of automatic hyper-legibility (I’m skeptical about that being worth anything like the investment most companies put into it to begin with, but that’s another topic) but all it does is shove important communication into side-channels and make the ticket-tracker an extra chore, not a work aid.
Like if you’re often having to hound developers to update tickets (a thing in every single place I’ve worked) they clearly aren’t finding them a useful tool for themselves. You’ve wrecked that supposed use-case, it’s ruined.
It’s also the case that trying to serve both purposes, and in fact strongly favoring the PM + management use case, tends to make the UI for these things terrible for developers, contributing to their avoidance of them—the people who, ideally, would collectively be spending far more time in the tools than anyone else, are second-class citizens as far as those tools’ features and UX.
As a side note, as a developer I’ve never understood why other devs find updating tasks so hard. It’s super easy and makes you look good, and if I’d worked hard and not updated the ticket I can imagine that from my managers perspective it looks like I haven’t done much, that’s bad for me and I would get anxious and not want that. Should be simple, right?
I was the manager in this case, and I also hated JIRA with a passion. It's often the managers doing the alternative spreadsheets too and only using JIRA as necessary. I found you didn't need to "hound" developers with Phabricator and part of the hounding was me being hounded further up about it. Tools matter! Developers love automated organization!
If I hadn’t pursued things that initially didn’t click for me, I’d be missing out on what are now my favorite… everything, really, and still stuck with some things that are by-comparison so bad that I can’t believe I ever liked them, at least not to the degree that I did.
I don't dismiss new things off-hand. I explore them until I'm sure that initial distaste is real. And I definitely don't bash my head against them over and over, to the point of wasting time. We are not obligated to like anything on anyone else's account.
Limit options. If the only, say, film options are five movies they’re resistant to watching, it’ll take very little time for them to break down and try one.
You do also have to restrict plausible substitutes, like if you do this with movies you need to either cut off or do a similar thing with video games.
Worst case, they don’t try the things you presented, but do go outside. Oh no, what a tragedy, lol.
It’s best to be able to tell it’s trash, because if you can’t then it means you’re missing what you need to fully appreciate really good things, which is less than ideal.
But it’s totally fine to like it. Zero shame.
And it doesn’t make people bad who can’t tell the difference between trash and good stuff, they’ve just prioritized different (and, maybe, less, but who cares) stuff than you have. Though when they try to make recommendations it’s fair to totally ignore them. Even if you are looking for a particular kind of trash, you need a critic who can tell good from bad (but appreciates that even bad things have an audience) if you want a good hit-rate. And when those sorts start to opine that actually good things are bad (because they haven’t developed the ability to appreciate them) it’s fine to regard that behavior as boorish, because it is. It’s basically the inverse of snobbery, and yeah, it’s also shitty.
I have a iphone that died on vacation and was set to backup only on WiFi (I’ve since changed that setting, haha, whoops) and has a couple days of photos stuck on it that weren’t backed up. It boots and makes noise but the screen is dead. Uncertainty about how broken it is has kept me from paying the not-cheap cost to get a screen replacement, and I haven’t found a way to read its data over a cable without unlocking via the screen first (which doesn’t work, and its touch-sensing capacity also seems to be dead, so blind input doesn’t do it, or else I could probably unlock it with a couple tries and get it to connect to WiFi it already knows and do its backup, but it won’t do that without being unlocked)