you are viewing a single comment's thread
view the rest of the comments
[–] -3 points 2 months ago (2 children)

No one cares enough to update them thats the point but its still useful to be able to check at a glance if someone is wfh or not. I'm sorry this is such a challenging concept to you to grasp.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 2 months ago* (last edited 2 months ago) (1 child)

    the part that is challenging to me is why anyone expects that to actually work?

    have you been paying attention for the last 20+ years now?

    i want to say there was maybe a period of 5 years around mid 2000 where it did but microslop has been awful for decades

    and i can count on 2 hands the number of times the issue was urgent enough to need an immediate response regardless of what middle management thinks (and phone calls worked fine)

    so over working for bigcap company cultures and middle managers having too little actual work

  • source
  • parent
  • hideshow 2 child comments
  • [–] -3 points 2 months ago (1 child)

    By that logic dont bother implementing anything because what if it doesnt work.

    It'll work good enough for most and better than the current status situation.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 months ago* (2 children)

    or you know stop using overpriced miroshit products

    pay your workers well and treat them like adults

    and cut useless middle management

    sadly my company still uses ms but at least they nail the other two

  • source
  • parent
  • hideshow 4 child comments
  • [–] -1 points 2 months ago (1 child)

    You hate MS, I do as well but its not relevant to talk about throwing it all out. This is just about a minor feature release and lemmys overreaction.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 2 months ago* (1 child)

    ms literally pushed a vibe coded update that boot lopped multiple dev machines for a week before we resolved it

    technically it was fixed same day but only because we have regular nightly images and other machines

    that alone should be enough of a reason, this is just more shit on the camel’s back

    but so you know I’m not downvoting you, nothing you've said is unreasonable, I just really have no patience with current tech companies and clearly lemmy is sick of ms’ shit

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago* (1 child)

    Microsoft pushing a bad update and breaking dev machines is an issue with your it department. Every single OS pushes bad updates thats why you stagger your releases through rings so you can catch the issues early and minimise downtime.

    Imagine if we stopped using linux because of a bad update.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago* (1 child)

    don’t act like this is normal

    i can’t think of a linux release in the 22+ years that’s had a non recoverable boot loop

    and who says it wasn’t staggered? doesn’t do a damn thing for those in the release group

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago* (last edited 2 months ago) (1 child)

    You just said you recovered the windows boot loop.

    Linux breaks booting all the time. Its so common its every linux user knows how to fix it. Pick the distro and you'll find tons of boot issues after major updates.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago*

    yea recovered by reinstalling an image from before the update, the system was a complete brick otherwise

    it took microslop 3 weeks to fix their shit, google it if you are confused, it wasn’t a limited hardware exposure issue, it was bad code

    we’ve been running rhel stable for decades with never a single example like this, i’m not talking about one off hiccups, i’m talking about the entire main line being busted

    pulling an example of loops from some random linux unstable distro or beta is meaningless

    to claim otherwise is bullshit, again this is not normal, even ms hasn’t been this bad since early vista

  • source
  • parent
  • [–] 2 points 2 months ago (1 child)

    Why? Work from home, not work from home, the works the same. I can't understand how this changes how you work. Unless your employer is very bad at figuring out how to do it. That is the only conclusion one can come to.

    Your work does a poor job, so you rely on outdated work methods. There is no other way to look at this.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -3 points 2 months ago* (last edited 2 months ago) (1 child)

    If they're in the office we can talk face to face if theyre at home we teams call. You are actually beyond cooked if you're unable to understand this.

    If your job is as simple as receive instruction return output then I see how this doesnt change much but thats not every job.

    If you don't talk to people why even have an office? This change isnt for fully remote workplaces.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 months ago* (1 child)

    And you are demonstrating terrible work habits.

    It should not change how you work. That is the problem, for some reason it does for you, meaning your work, or you, do not know how to work efficiently.

    And to be fair, if your work doesn't fix this problem it really isn't your fault. They should be nipping this crap in the bud and calling it out. Re-training people and getting productive.

  • source
  • parent
  • hideshow 2 child comments
  • [–] -1 points 2 months ago

    You still havent given a single reason. You just spout the same shit over and over as if you're some authority on the topic and we should all just believe things are the way you say they are.

    Im sure you are very hard to work with and once this feature is rolled out you'll still get no one coming by your desk.

  • source
  • parent