• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • And then interrupting that hold music at seemingly random intervals to tell you that they care about you, or to tell you that you could do this faster on their website.

    I had to call Assurant recently because their website literally threw an error and told me to call in and wouldn’t let me proceed. I was told by the automated messages no less than 4 unstoppable times that the website is faster, and then after explaining the situation to the person she told me that the website is faster.

    She was clearly reading the script and it’s not her fault so I kept quiet, but I have rarely felt such extreme rage in my life.




  • I have a similar one! I did house calls. I got called out on a warranty call, someone said a coworker of mine didn’t fix the problem. I look in the notes and the coworker says he did a standard virus removal, suggested virus protection but was turned down.

    I get there and sure enough it’s riddled with viruses again. Coworker was legit, notes all in order, I tell the client that this isn’t a warranty issue, the work was done, and it has now been reinfected and will need another removal. He seems fine with this, but his wife flips out and demands I prove it got reinfected.

    I suggest that we can check the web history. Since it was popping up ads, we’d see when the pop-ups started, and more importantly we’d see if they had stopped after coworker left. Guy says that’s unnecessary, it definitely got reinfected, and this time he’ll buy an antivirus. Wife is having none of it, says go ahead and check and I’ll see the problem was never fixed. I ask if they’re sure, guy kind of resignedly says to do it.

    I’m not one to kink shame, but when all the trans porn site titles came up, the dude was clearly mortified. I didn’t get very far into trying to figure out if I can prove it’s related before the wife says “just fix the damn thing” and stormed out. I hope it wasn’t too bad for him, she seemed a bit difficult to deal with.


  • It’s not entirely unlike my plan: No more externalities. That’s the big problem with the environment and with a bunch of other things. Economists call it an “externality” when the things you’re doing have side effects that you don’t have to account for, such as pollution.

    The thing is, we let industry and capital get away with it for a long time. And there’s no doubt that fixing it would also impact people. If the cost of properly disposing of a tire was built into the price of the tire, it would be passed along to customers. But it’s the only way to rehabilitate ANY system that uses currency.





  • psivchaz@reddthat.com
    cake
    toProgrammer Humor@programming.devMy Git Knowledge
    link
    fedilink
    arrow-up
    3
    arrow-down
    5
    ·
    4 months ago

    All these comments and no one is going to point out that this is invalid?

    The git stage and git commit don’t have any terminator, so it’s all one “command” and will fail. Then there’s a single & between git commit and git push, so it would run in parallel, so it would also fail.

    Also, don’t git stage . people. Or at least do a git status before to make sure you didn’t stage file-with-all-the-production-secrets




  • I agree but I think it needs to be slightly more practical. Sometimes a line of business just dries up and it would damage the company to try and keep that service going. It wouldn’t make sense to force a company into bankruptcy to keep one line going that few people use anymore.

    Earlier today, though, I was thinking about sunsetting guarantees. Companies can and should decommission things when it makes business sense, but the user generated content it has gathered shouldn’t just disappear, and they shouldn’t be allowed to destroy the user experience of things people have bought.

    So I would propose rules like:

    • If a service is being decomissioned or an entry point to that service being shut down, the content available on that service must be made available as a bulk export. Personal data, such as account data, messages, etc should be made available to users individually, while publicly accessible content should be made available publicly.

    • If a public service is being taken down completely, source code should be made available publicly.

    • If the service for a device which was physically purchased by consumers is being taken down, an update must be provided to allow users to use a local or alternative backend service. The source code for the service must be released publicly.

    • If features are being removed from a service which backed a physically purchased device, an update must be offered which allows users to point to a local or alternative service for either all functionality or, at minimum, the removed functionality. Looking at you, Google, keep removing features…