Thread: Internet Tablets in the Workplace
View Single Post
Nathan is offline Nathan
2007-12-12 , 19:16
Posts: 452 | Thanked: 522 times | Joined on Nov 2007
#37
Originally Posted by Hedgecore View Post
I'm glad this took a turn for civility again. I'm actually not too paranoid about security, given the chance to use my tablet I would in a second. I'm arguing points on both side of the coin, and I'll (much to your dismay/mental health) regularly switch sides. (That's how I explore a topic fully.)
LOL, I love technology -- hence my purchasing a N810 when I can (The dev codes hopefully will be live on the 15th). I plan on using it at work, and I'm sure the other IT guys will see it and want one too. They got Moto-Q's because it was cool. Just wait until they see a N810 in action. ;-D



... but in your career paths, you've had to see the other side (which is what I was pointing my finger at). The developer who doesn't need admin rights for any reason but insists on them because it's an affront to his perceived intellect.
Security based on "who" you are is not good. Security based on "what" you need is. I'm all for making the CEO/CFO mad by removing their network security that they don't need. ;-)


The one who wants to use his own machine for no other reason than to set his own standards and play by his own rules regardless of the impact it would have for another department
Depends on circumstances. If he actually impacts other departments then yes that is a problem. If he makes other departments uncomfortable that is their problem. For instance we have a set way to manage source; it is followed. This impacts any developers that work on that source base. However, on some projects we only have one developer and he has control of the build process -- as this really does not effect anything "globally". Others we have a set build process since it is multiple people (typically automated). Analyze the need and give the responsibility to those that "can" and "do" want it. Those that don't want it or can't do it don't.


(say, the one charged with maintaining everything - - IT).
Ah, see I look at it a bit differently -- if you give someone the right to customize their machine (such as I do for the devs because of the productivity factors) -- The only thing I require from IT department to do is rebrick the machine if the developer doesn't know how to. With Power comes responsibility. You mess it up, you fix it. If you can't fix it you get to rebrick it. And that loss of time is yours. Keeps everyone accountable. ;-) For our CS department, the machines are fairly locked down. They don't need that "freedom" (nor do many of them want it) and then IT fully supports their configurations. Right tool for the right job...


The one who comes up with ideas not because they're helpful but because they're grandiose and are a challenge as opposed to the usual daily code, and subsquently delays the project because rebuilding the wheel didn't work (like it didn't last time and the time before that).
I think I might also take a different look at this. I really don't like the Not Invented Here syndrome -- however, occasion for a new developer I will let them do it and then I have a "teaching" opportunity. ;-) Sometimes the cost for getting that teaching opportunity is worth suffering a NIH loss. ;-D


It's been brought up before but in business it comes down to accountability. You might be frickin Linus Torvalds but if IT can't guarantee that your linux tablet is secure, they can't in good conscience allow it on the network.
Wow this must be one of the few Windows places that actually removes/blocks internet explorer, active-x. I haven't heard of that many places taking that tough of a stance on security. Color me impressed. I wish I could get my company to ban it -- it would sure help security wise...


(And in my specific case, all devs do have widescreen laptops which still kicked the crap out of that rogue machine specs-wise - - the guy was just being difficult and wanted to use the tools for his own on-the-side efforts.)
See, then that makes a bit more sense why you are balking at adding another machine to the network. No good reason = no! Do your devs get to bring their notebooks home? Do your devs get local admin rights?

Nathan.