I work in IT. We donβt run CS here, but a bunch of clients of my old employer do. I had just shitposted about this fiasco in a discord server populated with fellow techs from that company, fired up lemmy, and this was the first post. What a fucking banger! I immediately shitposted again pasting this image. Youβve made my day. I need to stop using the internet because itβs all downhill from here. Thank you.
Fun story, my company just kicked off a PoC with crowdstrike 2 days ago. So far my computer was the only one that the agent was on as we had other work that needed to be done and we paused the rollout to the rest of my team. I woke up to boot loop hell today. Got it fixed right away, but so glad we didn't roll it out any further. Not a good look to be starting a PoC with.
If it's any consolation, this is the first issue of its kind in the multiple years we've been using CS. Still unacceptable, but historically the program has been stable and effective for us. Hopefully this reminds higher ups the importance of proper testing before releases
For sure, my previous company I left last August ran CS for 3 years and we had no issues. Hopefully they hire a bunch of QA folks that were probably part of the layoffs earlier this year.
I mean it seems almost impossible that they either didn't have a staging process to test N number of machines either virtual or otherwise or it passed through but it just seems insane that a problem of this magnitude went out to this many people.
I work in IT. We donβt run CS here, but a bunch of clients of my old employer do. I had just shitposted about this fiasco in a discord server populated with fellow techs from that company, fired up lemmy, and this was the first post. What a fucking banger! I immediately shitposted again pasting this image. Youβve made my day. I need to stop using the internet because itβs all downhill from here. Thank you.
Fun story, my company just kicked off a PoC with crowdstrike 2 days ago. So far my computer was the only one that the agent was on as we had other work that needed to be done and we paused the rollout to the rest of my team. I woke up to boot loop hell today. Got it fixed right away, but so glad we didn't roll it out any further. Not a good look to be starting a PoC with.
If it's any consolation, this is the first issue of its kind in the multiple years we've been using CS. Still unacceptable, but historically the program has been stable and effective for us. Hopefully this reminds higher ups the importance of proper testing before releases
For sure, my previous company I left last August ran CS for 3 years and we had no issues. Hopefully they hire a bunch of QA folks that were probably part of the layoffs earlier this year.
I mean it seems almost impossible that they either didn't have a staging process to test N number of machines either virtual or otherwise or it passed through but it just seems insane that a problem of this magnitude went out to this many people.
Something something first law of robotics