At my current place of employment, no one has ever quit or been fired. Every hire is still here.
In an office (with actual doors), perhaps, but an open floor plan solution is to save money, not to increase collaboration. All research articles I have noticed over the years conclude that productivity plummets in an open floor plan solution. If there is a job description it is suited for, I have yet to see it mentioned. The upsides of collaboration and camaraderie is obliterated by noise levels and disruptions.
Personally, I stay home and keep email closed and my phone off if I have something I actually need to get done in a timely fashion. It's the only way to get actual work done. At the office I have the best noise cancelling headphones money can buy (well, according to the reviews).
Where I live, three months is the norm. The law stipulates from one to three months, depending on how many years you've been working at the same place, but I have yet to work anywhere that operates with anything but three months notice after the six month trial period.
To be honest, if my password is a 30 character one that takes me several minutes to pull up on my computer's password safe and type in using a phone's keyboard, it doesn't take very often for that password to be dumbed down to something more convenient.
The problem is that password is not protecting the phone, but the account, accessible from anywhere. Dumbing down the password is a bad solution. I'd be equally happy with a middle ground, like a PIN code to purchase as opposed to the full password. Which, incidentally, is exactly how people would avoid someone picking up their phone and "prank buying" in the first place (current security drama with regards to the lock screen notwithstanding).
Having said that, my Android phone has not asked me for my password since I bought it, and I am not bankrupt yet, nor can I remember seeing articles about people having issues.
I said *I* don't want. I'm not trying to impose my choice upon others. I'd much prefer Apple added a configurable option to cater both for people that hand their gear to kids, or people they don't know, or habitually misplace hundreds of dollars worth of kit, as well as for people like me that do not.
As I said, it has gotten better. But it's not that long since it asked for a password simply to update an already installed application.
And, no, I don't want it to ask me for my password when I buy something on a device I have previously authenticated on. Tell me the price and ask for confirmation, yes, but ask me for password, no.
Indeed, the last time I can remember having to enter my Google password for my Android phone, was when I bought it. And that's why it's a randomly generated password of some length (and two-factor protected). My AppleID is.... not.
Apple could have solved this in so many ways that are more convenient. Like, god forbid, letting the user decide between several options. That way I could get one I would be happy with (a confirmation dialog to avoid accidental clicks), and parents could get one they are happy with (password required when doing something that costs money). Apple really does not like multiple choices though, so it is what it is.
If I didn't have to type my password all the freakin' time, I might generate an actually secure one. Granted, iOS has gotten somewhat better with the latest updates- at least it doesn't ask me for every app update anymore. But, still...
In the largest company I've worked for, the written rule was to explain and comment (using a specific syntax), never delete. The unwritten/save-our-sanity rule was to delete if the comments began affecting the readability of the code.
When working on code with hundreds of other developers, code that's commented out and explained/linked to a case id, can save a _lot_ of time. Say a piece of code solved an issue, but in turn created a performance issue. This did not become apparent until the code went live. The developer tasked with figuring it out isolates the affected flow and "... oh... someone added that credit check here a few weeks ago, I'll check that out first." That saves a lot of time compared to identifying dozens of involved files, then only diffing the specific methods involved in the particular flow.
They're going after the Usenet providers as well, via automated DMCA takedown requests. The providers have no choice but to comply (and to keep up, also automating the process), which means content is effectively gone within hours of being uploaded.
The irony when it comes to TV shows/movies is the same as it used to be with the music industry: the stuff being downloaded is largely not available to buy online legally. I wish they would put their efforts into making this content available for purchase instead of wasting their time trying to stem the flood of copyright infringement.
In defense of the diagnosis: when the inability to process social cues impairs your ability to function in society, it is a disability. One can argue that society has its head up its collective arses for being so rigid there's virtually one right way, and one only, to respond to any given social situation. But those are the rules we have to live by for the foreseeable future.
That would depend on where you live. Where I live and work, my employer isn't even allowed to check my email without a good reason. The same applies to all "personal areas". The hard drive in the computer the company has provided for you, is considered such an area. The assumption here is that there will always be _some_ personal use of a computer an employee sits at all day and often brings home or on trips with them. And a person has a right to privacy that the employer cannot invade without cause.
On the topic at hand, no place I have ever worked would dream of just handing a computer on to the next one in line without first reinstalling. So the employee wiping it before turning it in would be just fine. Last few jobs I've had, I've Truecrypted my computer (at the start of my employment) and handed it over in that state without any issues.
I said "here's what I think". I didn't say I had researched the agreements and could offer a contractual way to accomplish it. I believe a clause to enforce updates for a certain period (12 or 18 months, was it?) has already been added. I don't feel it's inconceivable that the manufacturers might also open their phones up at end-of-life. Come to think of it, doesn't HTC already offer a way to unlock their _new_ phones? Last I heard it was supposed to launch in the Aug/Sep time frame.
Enforce a policy where handset manufacturers are required to offer a convenient way to optionally install vanilla Android. Problem solved, as far as I'm concerned. When "primary" support is ended, I get the option of buying a newer device to get the manufacturer added bells and whistles, or going with vanilla Android until the hardware just can't handle it.
What did you think I meant with "configurable", if not exactly that?