What the F are we doing!?
11 replies (most recent on top)
@jh The problem is now mostly impacting nonintegrated AEs. We were in the middle of our MBO project due EoY and we've been completely blocked for over a week with no end in sight and no direction or ETA to resume work.
If you can't follow the ancient rule to use the internal artifactory you are a disgrace and should be fired. If you are still pulling from external sources and managed to pass security audits you are probably a perjurer too!
100X time waste
Enjoy the down time while they waste away productivity.
Hey no problem, we've got the 100x d1psh1t now.
@ar Sounds pretty relevant to a layoff board then, good thing we have this topic for you to discuss it.
@a6 maybe if one team keeps getting brought up with self-inflicted overreactions and problems they should be laid off
@a3 Last week on Wednesday all teams were advised to halt development & deployment due to the NPM supply-chain attack that impacted specific versions of some packages. AFAIK deployments could resume as of Friday so long as your images come from repo1/SaaS artifactory. But communication has been spotty on this.
I don't think development is still halted but maybe OP has a different communication they received. It was a gross over-reaction by ESRO regardless.
@a6 One team's issues? This was company wide dude, not our fault you're illiterate and unaware.
I haven’t heard anything about any of this stuff. This website is supposed to be about layoffs not constant posts about one team’s issues.
Do you have any more info on this? ALL development across businesses in Optum?