BWAAA-HAAA!!!! And then we have those people that post on Twitter, Facebook, LinkedIn, and who knows what else, that they'll be making a week long trip to go on a vacation and then wonder why their house was ransacked while they were gone.
I don't know how things may evolve over time, but I do suspect that privacy and data handling will become more of a part of data professionals' jobs in the future.
I know it's not a part of a lot of data professionals' jobs but I've always regarded a person's information as being private even before the Privacy Act of 1976. That notwithstanding, it's a real tough thing for me to understand why some companies say they need my SSN. They say it's for a credit check yet when I call them up for help, they always ask for the "last 4 digits" of my SSN. Sure, there's ways around that but holy moly. I think people have greatly over extended what "For security and tax purposes only - not for identification" (written on SSN cards) actually means. It's only come to mean that you can't use the card as a form of identification.
Folks talk about some of the great strides we've taken with PCI and the like but despite the great effort there, it does little to ensure actual "privacy". I'm not sure that such a thing actually exists anymore.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs