I see nothing constructive about an annual pay and performance review. It’s a mainstream practice that has baffled me for years.
To my way of thinking, a one-side-accountable, boss-administered review is little more than a dysfunctional pretense. It’s a negative to corporate performance, an obstacle to straight-talk relationships, and a prime cause of low morale at work. Even the mere knowledge that such an event will take place damages daily communications and teamwork.
…. I see the primary purpose …. as intimidation aimed at preserving the boss’s authority and power advantage. Such intimidation is unnecessary
…. At best, the discussion accomplishes nothing. More likely, it creates tensions that carry over to their everyday relationships.
…. claiming an evaluation can be “objective” is preposterous, as if any assessment is independent of that evaluator’s motives in the moment.
…. The absurdity is even more obvious when bosses — as they so often do — base their reviews on anonymous feedback received from others. This illogic is highlighted in the contemporary performance-reviewing fad called “360-degree feedback.”
…. any critique is as much an expression of the evaluator’s self-interests as it is a subordinate’s attributes or imperfections[.] To my way of thinking, the closest one can get to “objective” feedback is making an evaluator’s personal preferences, emotional biases, personal agendas and situational motives for giving feedback sufficiently explicit, so that recipients can determine what to take to heart for themselves.
…. You would think that the person in the best position to help somebody improve would be his or her boss.
Yet, thanks to the performance review, the boss is often the last person an employee would turn to.
…. I believe it’s immoral to maintain the facade that annual pay and performance reviews lead to corporate improvement, when it’s clear they lead to more bogus activities than valid ones. Instead of energizing individuals, they are dispiriting and create cynicism. Instead of stimulating corporate effectiveness, they lead to just-in-case and cover-your-behind activities that reduce the amount of time that could be put to productive use. Instead of promoting directness, honesty and candor, they stimulate inauthentic conversations in which people cast self-interested pursuits as essential company activities.
via online.wsj.com
Category Archives: Uncategorized
productivity is function of system (Programmer Productivity? | Tobias Fors)
Productivity in software development isn’t controlled just by the individual, it is controlled by how several individuals interact with each other.
….
Yes, individual programming skill matters greatly. So does the ability to work effectively with others. It’s not either or, it’s both. And that’s still not enough. To be productive, programmers need a supportive environment, and I don’t mean (just) nice colleagues. I’m talking about being in an organization designed to maximize the effectiveness of those who work in it.
and from the comments, Bob Marshall/ Deming:
“some 95% of an individual’s contribution is a function of the system that they have to work within, and only some 5% is down to an individual’s innate talent and effort”
note to self: get maven nature on projects in (my)eclipse
myeclipse: v8.6
plugins/ software:
mavensupport for myeclipse (m4e)
maven integration for eclipse (m2)
now, if a project wasn’t “maven-enabled”, i often had to manually edit the .project file to make it so, even with mavensupport installed.
but if you also install “maven integration for eclipse”, you can right-click a project without maven nature and select “(m2) myeclipse maven -> enable dependency management”.
a last piece of the puzzle seems to be needed – i think i enabled some advanced option in m4e (might even have been seemingly unrelated, like advanced tabs in pom). but a coworker disabled m4e after installing m2 and then got the right-click option to enable maven for a project…
if you try this, let me know how it works out…
edit: it seems i only had to enter the maven settings (myeclipse -> maven), and then exit (apply). without changing anything… then the “(m2) myeclipse maven -> enable dependency management” option emerged…