Overtime, yeah, ok... My boss (a real punk of a Univ. of Phoenix grad) told me once: "You knew when you started working in IT that you're exempt from overtime rules."
Translated: I get to work 40 hour weeks for salary, then I have to regularly stay late, get up at 1am at least twice a week to fix some dumass developer's mistake and miss all sorts of family events without getting an extra red cent for my "dedication".
And they wonder why I'm showing up late and leaving early now...
Sad but true, My company abhorrs ex-military employees (just listen to the trash-talk from certain managers) and the guys that "get it done" are the ones being promoted, not people that know better than to install unlicensed software or build a server with a bunch of security holes left in just to meet the boss's deadline. We're filled with yes-people and junior staff that are promoted quickly because they'll do what they're told without questioning the results and fill positions for a lower salary.
It's disgusting what some companies will do during an economic downturn. Stupid, imho.
Packages are convenient, but sometimes one really should consider using source. For instance, some tools like lsof (great tool btw Vic!) have so many server-specific hooks that installing a generic package likely causes some amount of feature neutering. I try to stick with source when I have the time available to install it, or when a product "should" be customized for a particular system.
On the other hand, how many times can one stand to Config and compile only to have cc blow up or waste an afternoon debugging why make install fails...
Then there's the "well I finally got the bzip2 source, but I gotta build gcc before I can build bzip2 so I can unbzip the lsof source...":P
I have to throw the B.S. flag on this point. My current employer is outsourcing to India - NOT because of American education but EXACTLY because they can get 10 programmers for the price of 1. We are not hiring local UNIX Admins for their mathematical or engineering talent - only if they can "do the job" and say "yes" when told to do something. I can't count how many times I've had a DBA ask me why he can't use his whole 8GB filesystem only to find some num-nutz "Senior" Admin build a 8000 MB filesystem because they don't know binary math. But - hey - it was NEVER part of their interview...
Slashdot Mirror
I was gonna say... butcha beat me to it! =D
Overtime, yeah, ok...
My boss (a real punk of a Univ. of Phoenix grad) told me once: "You knew when you started working in IT that you're exempt from overtime rules."
Translated: I get to work 40 hour weeks for salary, then I have to regularly stay late, get up at 1am at least twice a week to fix some dumass developer's mistake and miss all sorts of family events without getting an extra red cent for my "dedication".
And they wonder why I'm showing up late and leaving early now...
This "highly paid professional" crap has to go!
Sad but true, My company abhorrs ex-military employees (just listen to the trash-talk from certain managers) and the guys that "get it done" are the ones being promoted, not people that know better than to install unlicensed software or build a server with a bunch of security holes left in just to meet the boss's deadline. We're filled with yes-people and junior staff that are promoted quickly because they'll do what they're told without questioning the results and fill positions for a lower salary.
It's disgusting what some companies will do during an economic downturn. Stupid, imho.
BTW - working on my MBA...
LEGOs... LEGI... kinda like octopusses...
Packages are convenient, but sometimes one really should consider using source. For instance, some tools like lsof (great tool btw Vic!) have so many server-specific hooks that installing a generic package likely causes some amount of feature neutering. I try to stick with source when I have the time available to install it, or when a product "should" be customized for a particular system. On the other hand, how many times can one stand to Config and compile only to have cc blow up or waste an afternoon debugging why make install fails... Then there's the "well I finally got the bzip2 source, but I gotta build gcc before I can build bzip2 so I can unbzip the lsof source..." :P
I have to throw the B.S. flag on this point. My current employer is outsourcing to India - NOT because of American education but EXACTLY because they can get 10 programmers for the price of 1. We are not hiring local UNIX Admins for their mathematical or engineering talent - only if they can "do the job" and say "yes" when told to do something. I can't count how many times I've had a DBA ask me why he can't use his whole 8GB filesystem only to find some num-nutz "Senior" Admin build a 8000 MB filesystem because they don't know binary math. But - hey - it was NEVER part of their interview...