|Just another Perl shrine|
Re^5: defining methods on the flyby Anonymous Monk
|on Aug 03, 2006 at 20:14 UTC||Need Help??|
Ahhh... I get it. You bought into the myth that because you're a programmer, you should be pampered and spoiled, and treated better than everyone else, because you're special. You're not like those non-tech scum, right?
It's crap; and the .com bust proved it. Pampering a bunch of spoiled brats leads to... no increase in productivity, and a bunch of pampered, but still spoiled brats. Silicon Valley leaks money like a sieve... most programmers aren't paid that much; I flat out refused to cash in on that nightmare, becaue I saw all the snake oil that was being peddled down there, and refused to be a party to bilking clueless investors out of their money.
It's because if you deskill a job; take away a workers pride in the job they do;
A worker should take pride in every job they do; the pride comes from doing the job well, not from being pampered. A real man learns to take pride in a floor well swept, garbage well cleaned, or anything done right. In coding, that includes code written to conform to the standards of his fellow man; not "rockstar" coders writing clever, unmaintainable code to tickle their own ego.
eliminate personal innovation, flair--and yes--ego from the workplace;
Whine, whine, whine! Your personal ego is not what motivates a normal person; the real motivation is to do the job right, so that everyone can understand it. Ego and selfishness lead to poor products; people do better when they co-operate, not fight to screw each other over.
you get the cheapest per-hour labour bills, because you end up with the dregs of the profession. Those with low skills, no motivation to improve, that "occupy" theirs desk for the statutory minimum hours to fulfill their job descriptions, whilst turning out the bare minimum of lowest quality work they can get away with
Blah, blah, blah... doom and gloom, lack of creativity -- oh, my! Programming should be a rote job; it's just the act of documenting a known solution to a known problem. The hardware guys build the machines. The mathematicians prove the algorithms work. The 0.1% in R&D design something new. Everyone else plugs in busines rules into business needs, adding the customizations to known wheels in known ways. It's NOT high art, no matter the typical programmer conceit.
Until you can replace your humans with robots as the car industry did on their production lines, you'd better invest in training your programmers to a high standard, and valuing their innovations, skills and yes--egos.
"Innovations" are overrated; the world is full of innovative ideas that just aren't practical to implement. Everyone and their dog has some great new, "world chaning idea". The tiny little corner that is R&D is the place to test those out; not the 99.999% reality that is the real business world. Skills are what matter; especially the skill of discerning what is compatible with existing standards, and how to conform to them. Egos should be left at the door in every line of work.
Show me a programmer who does it only for the money, and I'll show you someone who will be working for your rival next week or the week after.
Bah. A man works because the work is worthwhile, and the pay is worth it. If the rival has a better job, and/or better pay, then anyone will leave. That's just the nature of the market; programming is not special in this regard.