Internally people probably talked about how there were huge issues. Others probably said those issues are over stated and it’s no big deal. They decided to release it and the press says there are issues. Then, the company decides there are issues. That simple.
Having been the guy in an org shouting not to do something only for it to come back to us this way, the finger-pointing that begins is nuts. Often the people who tried to stop the “feature” from rolling out are the first to get blamed for it being shit.
Classic CYA, make sure everything you said is in writing somewhere.
I have as well. I won’t pretend I’m always right - I’ve thought some ideas that worked out incredibly were horrible. Also had the situation you describe happen. It’s okay when you’re working with reasonable people. Show them the slide deck, the email, the analysis, whatever… “Look you didn’t approve this”. "Here is an alternative ". That can work.
Just telling folks “I told you so” isn’t usually a great form of communication.
That’s just what we call people spending some time to figure something out. Security research is basically just trying to learn the technology and then trying to break it.
they needed researchers to tell them that?
Well . . . the smart people they ignored when CoPilot was first proposed.
It’s PR bullshit to give an excuse for backtracking basically
Internally people probably talked about how there were huge issues. Others probably said those issues are over stated and it’s no big deal. They decided to release it and the press says there are issues. Then, the company decides there are issues. That simple.
Having been the guy in an org shouting not to do something only for it to come back to us this way, the finger-pointing that begins is nuts. Often the people who tried to stop the “feature” from rolling out are the first to get blamed for it being shit.
Classic CYA, make sure everything you said is in writing somewhere.
I have as well. I won’t pretend I’m always right - I’ve thought some ideas that worked out incredibly were horrible. Also had the situation you describe happen. It’s okay when you’re working with reasonable people. Show them the slide deck, the email, the analysis, whatever… “Look you didn’t approve this”. "Here is an alternative ". That can work.
Just telling folks “I told you so” isn’t usually a great form of communication.
That’s just what we call people spending some time to figure something out. Security research is basically just trying to learn the technology and then trying to break it.
it did not take me long to figure out that maybe spyware that takes screenshots of what you’re doing is a bad idea
Agreed but someone actually tried it - did the research.