692
Joined 5 years ago
Joined 5 years ago
Understand the actual problem , write it down and repeat back to get confirmation.
write down the (non)functional requirements from the stakeholders, the exact scope of work before doing anything, again repeat back to get confirmation,
In the murky world of greyness where people do not really know information or the full set of data, agree (again before starting work) on little subtasks/ plans to get the information (PoC)
Write down the Risks/ Assumptions/ Issues/ Dependences of your actions and again get them signed off
all this takes time and can be extremely boring relative to getting stuff done, so a lot of people just do stuff they think is right
> That society is ok with that is a huge problem to say the least.
but you could compare any bad actor actions to ME/PSP and say it's the same or not as bad
it's bordering on Whataboutery
Once we have a list of ideas, then whittle the list down with the realist and pessimistic people of the group; until there's one obvious way forward or a couple of least worse ideas.
Generally most people are better at telling you what you can't do,
https://slate.com/technology/2015/02/lenovo-superfish-scanda...
I will never buy Lenovo again
https://www.verywellhealth.com/lead-crime-hypothesis-4147074
It's similar to imdb for movies, its a place full of opinions. I take everything with pinch of salt, but it's the best review site around
I genuinely believed at the time my mind would not be able to go back and I'd die or go brain dead (no psychedelics or drugs taken)
Another team would then assess and analyse the root cause from a company wide perspective and then assess the risks, costs and impact and then make any modifications (possibly redoing the temporary fix, and fixing it properly)
Real issue, a call center main telephony system and one of the management servers kept crashing causing over 1400 call center people to stop working. Temporary fix was to re boot the servers every 4 hours causing minor pain, but the call staff was up and running.
After a whole stupid week of the engineers not being able to find the route cause it was escalated extremely high and our team was brought in and we found the root cause in seconds (literally)The servers was VMs and the engineers hadn't checked the physical ESX server they were hosted on. another VM on the box caused the server to go unstable (ESX not configured correctly).
BAU project set up to audit/ report and fix all the ESX servers in the company for other stupid config issues
on the subject of prior work, and just thinking out loud, but I wonder if USPTO could set up some rules whereby the person asking for a patent has to do some sort of search for prior art, in order to get the patent
and if they don't or do it badly/ not to the rules, then a penalty is applied, financial or immediate ban on patients?
describes it very well. I was so freaked out by the thought of not getting back into my body, I panicked and woke my self up.
I believe/ heard that it can can recreated at will
you have to provide information and details from two of the following: Passport, last tax submission or driving licence
the sign up to the internet healthcare system used by my doctor seemed to be run by a 3rd party (not happy) needed general information and a picture of my passport or driving license. I declined, because it's a third party and I could not be bothered reading the large list of ways they will likely sell your data and partially because I don't need my doctors info online
I have made a couple of huge ones - luckily I kept my job