I've been wondering about this wireless charging business. It has to be less efficient than wired charging. Given the current push to reduce energy use, I'm at a loss to understand how people can be pushing wireless charging.

... is one who, once bought, stays bought.

My first thought, when I read the summary, was of my co-workers, all male, wearing short skirts or low-cut dresses. I may have to gouge out my eyes.

My personal experience is that absent clear enforced rules, deportment degrades over time to unacceptable levels, at which point management institutes unpalatable rules. If you have freedom in deportment, enjoy it but be sensible.

...why any "standard" would include patented technology. Seems like a very stupid idea. About the same as copyrighting the spelling of words.

Talking to the pros is only the worst thing to do if you know as much, if not more, than they do. The fact that the OP is asking slashdot indicates he does not know a lot about setting up storage in the PB range. Are the major vendors overpriced? In terms of the hardware you get, probably. In terms of the knowledge they bring to the table, probably NOT in the case of the OP. If you have someone who can select COTS components and effectively couple them with some good OS/SW, great. Otherwise, get someone who knows what they are doing and buy their solution. Doing it on your own when you don't know what you are doing will only end in tears.

From my perspective, the biggest problem with BYOD is that management is not likely to give IT the resources needed to ensure that BYOD is done in a secure manner. Personally, I will not bring my own device to work for a couple of reasons. First, why on earth would I subsidize my employer? Second, why on earth would I consider giving my employer any measure of control over my device?

This is not necessarily a problem. First off, the legality of some actions may depend on where the actions occurred. In the case of the drone, discharging a gun is illegal in some locales and legal in others. So, the authorities could well investigate where the drone was shooting. Second, law has gotten ridiculous; no cop - heck, no lawyer - is aware of all laws. See something new, like a privately owned drone firing a gun, maybe you want to check whether there are applicable laws. Now, fishing trips to find something with which to harass your ex, definitely a problem.

... but if you do it without Stupid's permission, Stupid may get angry.

That's certainly an option. But keep in mind that if you upset them, they do have the ability to make your life very unpleasant every time you cross their path. I'm not saying not to do it, just that you should do a cost-benefit analysis on the concept before you do it.

"The cloud is still basically a v1.0 product." Begging your pardon, but the cloud is really still 0.X.

Time to ban kitchen tables.

What do you consider "reasonable" access? I tend to be very conservative about it. If I can do my job, I consider that reasonable access. Anything not strictly required to do my job is simply a bonus. Under those definitions, I've never had a job that did not afford me reasonable access to the internet. I know that many people will consider "reasonable" access to include things like access to Facebook and twitter and their bank accounts, etc. I disagree. When I'm at work, I'm working. When I'm not at work, I'm not at work. I try very hard to keep the boundary distinct. the more I blur the line, the easier it is for my employer to want me to be always available.

Exactly. Even now, 2015, the vast majority of computer users are clueless. Since the nail that sticks up is the nail that gets hammered, I just hunker down. When (if) the majority of computer users clues in, I may change my policy. Until then, I keep quite. FWIW, if it was something truly urgent that really did require me to notify someone of an incorrect email address, I'd have my lawyer do the notification.

I'm not expecting that my boss will always do what I want. I will settle for the knowledge that when I say something, my boss actually pays attention to what I say and gives it fair consideration. If you want to lose me, ignore me (and then expect me to clean up the mess that occurred because you ignored me). Remember, you are the manager; you are NOT G-d. Your people do know more about some things than do you, and you know more about other things than do they. If you work together, you can maximize your strengths and minimize your weaknesses.

as long as you don't keep the weekly 1-on-1s running forever. They're great for a new manager to get to know his team. But the last thing I want to do is spend 15 to 30 minutes a week in an awkward meeting with my manager when we've nothing to discuss. Keep an eye on the number of meetings your developers are attending. If meetings regularly chew up a large chunk of developer time, you've got a problem. Conversely, if your developers never, or rarely, meet with anyone other than developers or you, you've also got a problem. Developers should be talking to their customers (i.e. the people for whom they are developing the software). Yes, in an ideal agile world, the customers would be right there with the developers. But, in 29 years (dang, has it been that long) as a developer, I've yet to encounter that.