the underlying driver for this kind of employee surveillance is still typically profit.
I don't disagree that the intentions at the highest level may be profit, but once it exits the mouth of the CEO that part is quickly lost in translation. The people at the high level are far too busy to be bothered with the technical details and just want a summary of whatever they're measuring so they can say "loss in profit wasn't us, our numbers look great!".
For example: say you're in charge of a department of 20-30 programmers. Upper management is given the directive "more profit". Upper management comes to you and says "your department needs to cut costs", and so the two of you agree on a way to measure this. They're smart enough to know that things like "lines of code" or "number of bug trackers" are easily gamed, so you agree that the metric you're going to use will be "cost per hour of coding". If you reduce the cost per hour of code, that means you've become more efficient right?
So the first thing you do is start making noise about outsourceing and find a coding sweatshop in india that will write software for $3/hour. You hire 15 indians to start cranking out code for you and boom! You just cut your cost per hour of coding in half. You use the fact that your brilliant management has cut costs in half to justify increased budget and workforce for your department, resulting in no need for layoffs. Your programmers continue to do what they were doing before, with the exception of tasking a few junior programmers who now have the assignment of gaining experience in writing requirements by keeping the indian sweatshop busy writing nonsense programs.
So in this example, while the original drive may have been profit the end result was basically a really overpriced requirements writing simulator for the guys you want to groom to become project managers.
No, they want to micromanage people in the name of profit.
No, profit doesn't have a factor in it, at least in what I've seen. It's just metrics for the metric god. The management bureaucracy wants to see numbers which they can then pretend to read like tea leaves. From that point they issue some nonsensical decree ("There are too many commits to the repository! Why can't you guys get your software right the first time! I want to see less commits!") and go pat themselves on the back for being effective managers. In the meantime, the employees who have to deal with that BS expend mental energy trying to make sure whatever they're doing results in good metrics, possibly at the cost of productivity and efficiency.
They buy a case or bumper to ensure that the screen and/or glass back don't get destroyed the first time the damn thing falls out of your pocket. It also renders the whole "thinner is better" thing rather stupid for similar reasons, as that "life proof" or "otter box" case is adding a hella whole lot more thickness to the phone than either a headphone jack or thicker battery.
My Nexus 4 (yes I still have it, no repairs required yet) has a bumper case that protects the outer perimeter but leaves the back uncovered. I love it because it protects the most common case for cracking the glass (dropping it on a corner) while not really adding much bulk or weight. I haven't been able to find similar cases for other phones though for some reason.
I was actually just being snarky and making a funny, but once you started to rant, it did make me happy that you weren't enjoying it.
Eh? The guy was sharing some good information that's highly relevant to the discussion on a subject he's clearly knowledgeable about. I find it kind of sad that on a site supposedly for nerds, you confuse an infodump for a rant.
I had the good fortune of being able to work on the most interesting parts of our projects and to participate in business development. That gave me the advantage of knowing what contracts we were hoping to win and what technology I needed to know to keep myself employed.
That part is key. I've been doing defense contracting for a while now and as much as I hate all of the business and management stuff (I just want to build things and then blow them up) I've always had an ear out for the business development side and it's served me well. Knowing what's coming up next not only allows me to build skills in that direction, but it also allows me to look for places where work I'm doing on one project can also be used on an upcoming project with minimal modification.
3) Defense Contracting - if you can get a security clearance, there is abundant work where defense contracts are strong (around DC and military installations.)
This is a really fun option. Generally in the defense industry there's a sliding scale between stable/boring production projects and unstable/exciting R&D projects. Get on the R&D (like real "make something new" R&D, not "we're going to make a minor improvement on an existing product" R&D) side in a big company and you'll never be bored.
The bigger issue with California is that it had so many wasted votes; over 3.4 million Democrats in the state could have stayed at home with no change to the winner of the state.
As an interesting corollary to that, a lot of republicans in california do stay home for exactly that reason. The state is so overwhelmingly democrat that voting (at least in the presidential part of the ballot) feels kind of pointless. I personally voted 3rd party because I knew a republican vote wouldn't matter. One of my friends wrote himself in and got a few tens of otherwise republican voters to write him in too for the laughs. I wouldn't be surprised if the same sort of thing was happening all up and down the state. Probably not enough to account for multiple millions of votes or actually make a real difference, but I'd bet it's enough of an effect to show up in the stats.
By "black supremacist" you mean an African-American who is concerned they are far more likely to be unarmed and yet still shot to death by a police officer than a white American.
I'd give him the benefit of the doubt and say he means the actual black supremacists, and not whatever strawman you're thinking of. Or are you under the impression that only white people are capable of being racists?
Apparently you're just as dumb if you think just knowing the regular IP is going to fix shit with a hosed DHCP config..
Please quote the part where I said knowing "the regular IP" (whatever the hell that's supposed to mean) would fix a hosed DHCP config. For all you know I was referring to people who jump to conclusions.
Long computations which yield zero are probably all for naught.