Re:Work versus Life. Greatness versus Family
by PaulHoule on Thursday October 24, 2013 @07:37AM
(#6604611)
I have had some cases where recruiters gave me an easy way out of a bad job. I've had some recruiters place me in a position that doubled my pay and challenged me towards greatness. Another recruiter gave me a really hard sell when I owed the IRS a lot of back taxes... If it wasn't for me they might not have pared down the project plan to something achievable and the might never have gotten the i's dotted and t's crossed and got the product in the hands of the customers, but my boss very specifically denied me recognition for my success.
The average recruiter, however, is filling a hole that is left behind by somebody who burned out. He's hoping that you can hit the ground running without any training, which is rarely realistic, particularly considering that 80% of programming work is doing what management expects to deliver 20% of the value. Because they haven't trained any of the other people working on the project you'll find that it's difficult to get any questions answered of the order of "how do I get this build consistently?", "how do I get this to build in less than an hour?", "which module is the right place to add that functionality?", "which applicationContext.xml file actually gets deployed to the assembly and how?" and stuff like that..
In a case like that you're set up to fail and you need to "think different" and start with the 80% of the work that gets you 20% of the way there, and then when the special job comes around where you're the best in the world you can sprout solutions like mushrooms.
The average recruiter, however, is filling a hole that is left behind by somebody who burned out. He's hoping that you can hit the ground running without any training, which is rarely realistic, particularly considering that 80% of programming work is doing what management expects to deliver 20% of the value. Because they haven't trained any of the other people working on the project you'll find that it's difficult to get any questions answered of the order of "how do I get this build consistently?", "how do I get this to build in less than an hour?", "which module is the right place to add that functionality?", "which applicationContext.xml file actually gets deployed to the assembly and how?" and stuff like that..
In a case like that you're set up to fail and you need to "think different" and start with the 80% of the work that gets you 20% of the way there, and then when the special job comes around where you're the best in the world you can sprout solutions like mushrooms.