I don't expect you to be head of that department for much longer.
"Why haven't you upgraded our systems to $superawesomestuff$ yet?" "I run this department damnit, we don't do that because I've decided its wrong." "Well go decide its wrong on your own, significantly increased, free time."
You work for the company, not the other way around. I doubt it's your decision to make a moral judgment and dictate that to everyone else.
I've been getting better results recently from ask.com then googles search. Googles results are flooded with useless blogs, it's hardly the best search engine, just the most popular.
Well, unless you're trying to make a completley open OS. In which case 'better' documentation and support doesn't cut it when parts that are required to make hardware work are closed and are only accessable via a NDA if at all.
Theo gets irritated because companies claiming to support open source do not when asked to.
... that you would get paid close to what you bring in to the company? That people never leave them with a bad taste in their mouth? That because you had a bad week the business model must be flawed?
The only real difference between working in an outsourcing IT company and working in a cube is guarenteed hours.
Of course it will. They'll just raise prices for 'another' reason. Just like it's illegel to fire someone for being gay. If you want to get rid of them for being gay, you just give them another reason and let them go.
No, they suggested that if they installed software the customer did not ask for and without their approval and that ended up being a security problem for the customer then the tech may be, and possibly should be, liable. It is a little different situation then the customer paying you to do something specific and you doing that specific thing.
Why not just do your job and fix their computer like they asked you to. Would you like your waiter to try and convince you to change your order because they don't think it's right to eat lamb?
Critical problems are not held back until patch Tuesday. However they are not released until at least some tests have been run on them, and no admin with even a single brain cell would install a patch just because someone said it's critical without testing it on their own environment.
There will alawys be a time difference between a problem being found, a patch being released and finally that patch being applied. Having a single day where most patches will be released allows large sites to properly schedule testing and deployment of patches which will speed up the installation of those patches.
Slashdot Mirror
Apperently you don't.
Blaster First Release date: August 11, 2003
Patch that fixed what Blaster exploited date: July 16, 2003
SP2 Release date: August 6, 2004
People who want to play DX10 games. People who like the latest and greatest of everything. People.
And admins who want to administer printers using the Printer management tool that came with 2003R2 without logging into a 2003 server.
No one will ever create something people like better then the iPod, and no one will ever want a computer in their home.
I don't expect you to be head of that department for much longer.
"Why haven't you upgraded our systems to $superawesomestuff$ yet?"
"I run this department damnit, we don't do that because I've decided its wrong."
"Well go decide its wrong on your own, significantly increased, free time."
You work for the company, not the other way around. I doubt it's your decision to make a moral judgment and dictate that to everyone else.
I've been getting better results recently from ask.com then googles search. Googles results are flooded with useless blogs, it's hardly the best search engine, just the most popular.
SGI
Well, unless you're trying to make a completley open OS. In which case 'better' documentation and support doesn't cut it when parts that are required to make hardware work are closed and are only accessable via a NDA if at all.
Theo gets irritated because companies claiming to support open source do not when asked to.
... that you would get paid close to what you bring in to the company? That people never leave them with a bad taste in their mouth? That because you had a bad week the business model must be flawed?
The only real difference between working in an outsourcing IT company and working in a cube is guarenteed hours.
Ya, the Debian people should ignore their own ideals because some pimply faced teenagers think it's cool to hate Microsoft.
How dare they offer new products!
I guess you don't run applications on your systems, just OS's.
This is even remotely interesting because?
My guess is there are a lot of team member introductions.
Magic
Someone explain to me how that applies to Digital Cameras pixal density.
No, they suggested that if they installed software the customer did not ask for and without their approval and that ended up being a security problem for the customer then the tech may be, and possibly should be, liable. It is a little different situation then the customer paying you to do something specific and you doing that specific thing.
Why not just do your job and fix their computer like they asked you to. Would you like your waiter to try and convince you to change your order because they don't think it's right to eat lamb?
I suppose you could if you like asking for already included features
Critical problems are not held back until patch Tuesday. However they are not released until at least some tests have been run on them, and no admin with even a single brain cell would install a patch just because someone said it's critical without testing it on their own environment.
There will alawys be a time difference between a problem being found, a patch being released and finally that patch being applied. Having a single day where most patches will be released allows large sites to properly schedule testing and deployment of patches which will speed up the installation of those patches.
More crap on the TV.
Firefox stops DDoS's now too? IE is the only way to infect a machine?
Your fingers broken and you can't type google into your address bar?