2,041 karma · joined April 2, 2011
Is there anyone on hand who could explain how what looks very much like a social engineering attack is not "human research"?
Secondly, I would regularly give a speech to the finance employees that went like this:
“In this business, we may run into trouble. We may miss a quarter. We may even go bankrupt, but we will not go to jail. So if somebody asks you to do something that you think might put you in jail, call me.”(Your ISP classifies as a middle man as well...)
* You want means to keep all of the dev environments in sync so you don't get "works on my machine" problems.
* If you update something, then you need a way for everyone to have their environment reconfigured.
* As the number of projects/stacks/developers scales this becomes a bigger and bigger issue.
I've used some Anisble in combination with a shell script wrapper to handle some of this kind of stuff. Even still, it takes a lot of hands on support to make it all work. So, if you can get something like this to scale, it might be a big win ... if...
(edit formatting.)
Edit: I think this might be it: https://www.bbc.com/worklife/article/20191115-office-noise-a...
Attack the person does very little for you except in a purely emotional venue. It can actually make things much much worse, particularly when there are already strongly held beliefs involved. All it does is further polarize an issue in peoples minds and make it more likely that they will hold faster to their beliefs. (i.e. the attacker reinforces the mistaken belief in the attacked's mind and makes them even less likely to respond to a logical argument.) That's how you turn loud voices into a dangerous situation and do it fast. (In other terms, that's how you turn an argument/discussion into a fight). This is true in pretty much every context.
https://fs.blog/2014/10/the-ten-golden-rules-of-argument/#:~....)
Basically, you need a deployment methodology that allows for: * Ease of use by "novice" developers * Only introduces minimal overhead for those developers * Makes it easy to upgrade or remove a tool you installed 6 months ago * Doesn't require a tool development team to come up with their own solution
This is a surprisingly tricky to do on a diverse environment with 1000+ internal users.
I live in Texas, a good chunk of the year, it would be nuts to try to live without A/C (We're not quite Death Valley, but it can get pretty hot here ...). So, I'd amend that one to:
"Open the windows and turn off the A/C"
I really like the few months a year where I can do this and not get cooked!
This kind of knowledge is highly perishable if you don't use it everyday. You quickly find yourself moving from "knowing" something to "knowing how to find" an answer to "how did that go again?". It's just the nature of the business.
It doesn't mean you aren't good at or capable of picking those things back up, it just means you may need a quick refresher. Not being allowed to use references makes that artificially worse.