But for the love of Darwin, NOT SYFY
Actually, you make sense. In my other post I said we should hold the shooters accountable, but I failed to consider the 'unintended consequences" of that, which was dumb as I usually try to.
Bad example.
You do have the right to yell "fire" in a crowded theater. But if you are wrong, you will be held liable.
You also do not have your right to speech preemptively oppressed by requiring a license to speak before you speak, or have your background checked or neighbors interviewed before you speak, as occurs with people purchasing firearms.
Taking "shouting fire in a theater" analogy further, it would require everyone to have a federal background check and a state license before operating a printing press, or speaking in public at all, just in case they might print or say something wrongful or injurious.
Holding people accountable for their wrongful or injurious behavior is one thing. Assuming they will engage in wrongful or injurious behavior before hand is another. I did not see screams of outrage demanding pre-licensing for speech after Al Sharpton destroyed a man over the Tawanna Brawley incident. Or the Richard Jewel story. Or Ray Donovan. Or any number of people falsely accused and maligned in the press or public in general.
We should blame the construction industry?
Ban home remodeling?
WTF?
The shooters tried to put the fire out and called 911. They acted fairly responsibly, though with some forethought they would have taken some preventative measures to prevent sparks.
Sometimes stuff happens. Using it to promote your particular social engineering agenda is bullcrap.
As another poster said, hold the shooters responsible for this. If there are not already laws in place that do so, there can be fairly quickly.
Fine. What about people without Exchange?
I need to sync my personal outlook with my personal phone. I need to do it without a third party involved.
Why? Because I use my personal phone for work. I do not want my corporate information filtered through someone else server, (iOS, Android), and I do not want my personal information filtered through my employers server, (Exchange, Blackberry).
My employer would not be happy if meeting notices about the back-end system I might be working on for the major new service offering were to show up on Google servers, or anywhere else. And I sure know my employer has no business knowing what I do evenings or weekends. (my employer is a very large company in a very competitive sector)
Currently, my Symbian phone, as well as old win6.5(?) phones can synch with Outlook on my PC over Bluetooth, (also cable and infrared if I prefer). No third party server needed. They both do this without any manual intervention. As soon as I walk within range, my phone connects to my laptop and syncs directly with it, without a third party server involved*. The last I checked, iOS, Android and Win7/8 require use of a third party server, and in the case of ios and android they do not sync everything in outlook.
Why would Google, Apple and Microsoft all take away existing functionality and now require that this information be sent through a third party server? I suspect the question answers itself.
*(This is using the last version of Nokia's PC Suite, as even the replacement tools OVI and Nokia Suite have removed some of the original functionality, like one way sync)
I use an artificial rain storm I downloaded a few years ago from http://simplynoise.com/ . I see they have a new version.
I use headphones in the office. They have developers mixed in with everyone else, phone reps, managers, everyone but sales staff. So it can get very noisy.
I tried white noise, pink noise and brown noise, (which they also have), but all hurt my ears after a while, when using headphones. I find the artificial rainstorm does not. I put it in a repeating loop and it takes care of suppressing office noise. this is especially effective when combined with noise cancelling headphones.
I find music too distracting, whether rock, classical or something else, like Phillip Glass, Sigur Ros, etc. People do not believe me when they ask what I am bouncing around to in my chair and I say Naqoyqatsi or Edgar Meyer. But the rainstorm does not distract and does allow me to concentrate.
I currently work for a company that has instituted an incredibly restrictive development methodology they bought from a big consulting firm. It requires multiple forms be filled out for every program written, every requirement for every program written, every request for every change to every program or application written. All of these reviewed by coworkers who are not about to alienate team members, and reviewed by lower management who want to look good to upper management by having everything go smoothly.
These documents are then stored on the LAN. To never, or rarely ever, be read again.
The one thing it does not enforce or require, is meaningful documentation in the code itself.
It doubles, or more, the time it takes to do everything. But it does nothing to stop the mistakes any better than the procedures that went before. If anything, it finds less errors, because we were not given more time to do this double or more amount of work. So time is so compressed, we do not have time to do anything other than get it working and get it in.
One thing it does do very well, is prevent problems from getting fixed. The only people that will start a change effort are those that notice a problem and are affected by it enough to have it cause them problems. Otherwise no one wants to go through the bureaucracy to kick off any sort of change effort, which leaves a lot of ticking time-bombs in the infrastructure configurations, application designs and application code.
The only place documentation is good, is if it is meaningful, and in the code, where it is readily findable and far less likely to get lost, short of some fool deleting it.
Documentation located anywhere else will be lost, or obsolete many more times than not, before you ever really need it.
If anything, documentation in code should be reviewed by people with absolutely no connection to the application it is for. If it is good enough for them to figure out an understand what is being done, and more importantly why it is being done, only then is it worth anything more than the bytes is written with in storage.
Variables don't; constants aren't.