Re: The Passive-Aggressive Programmer: or Why Nothing Gets Done
by edw519 on Saturday June 14, 2008 @05:46PM
(#217705)
Interesting examples of the "PAP". A good follow-up might examine why a programmer is passive-aggressive.
thaumaturgy hits on one common reason: the programmer is a product of his environment.
Another very common reason is that the programmer is in over his head and uses "fog" to protect himself. Why? It's easier. And it works. Problem is that the programmer has done nothing to get out from being in over his head. And probably never will. They're everywhere.
My first mentor once told me why he thought there were so many mediocre programmers: all they have to do is stay one step ahead of the user. In a commercial environment, not so hard to do.
thaumaturgy hits on one common reason: the programmer is a product of his environment.
Another very common reason is that the programmer is in over his head and uses "fog" to protect himself. Why? It's easier. And it works. Problem is that the programmer has done nothing to get out from being in over his head. And probably never will. They're everywhere.
My first mentor once told me why he thought there were so many mediocre programmers: all they have to do is stay one step ahead of the user. In a commercial environment, not so hard to do.