Уровень 0 · материалов: 4
В кластер входят документы, посвященные вреду применения жестких метрик и денежных стимулов к творческой работе, и не входят документы об игнорировании экспертов ради внешней привлекательности системы.
Общие признаки: неэффективность количественных показателей, проблемы управления в интеллектуальном труде, подмена качества количеством, вред внешних стимулов и бонусов
Группа выше: Критика корпоративного управления
Смысл: The main idea is a critique of the attempt to apply rigid, quantitative industrial metrics to creative and intellectual work like programming. It highlights the 'cobra effect' or Goodhart's Law: when a measure becomes a target, it ceases to be a good measure, as employees will find the path of least resistance to maximize the metric regardless of actual value delivered.
A satirical look at how software developers consistently game quantitative performance metrics imposed by out-of-touch management.
Смысл: The main idea is a satirical critique of the 'Dunning-Kruger effect' and poor corporate management. It illustrates how valuing quantitative metrics (lines of code/speed) over qualitative results (functional, clean code) can lead to the promotion of incompetent individuals who eventually destroy the organization from within.
An experienced developer helps an unqualified colleague who, through arrogance and misleading productivity metrics, rises to management and replaces the skilled staff with unskilled typists, forcing the developer to quit.
Смысл: The main idea is that in intellectual and creative industries, traditional performance-based monetary bonuses can be counterproductive, as they undermine intrinsic motivation and are nearly impossible to administer fairly due to the subjective nature of 'productivity' in software development.
Joel Spolsky discusses why cash bonuses for 'million-dollar ideas' are risky and suggests that intrinsic motivation is more valuable than extrinsic rewards in IT.
Смысл: The text argues that individual performance metrics in IT are misleading because they ignore the critical value of collaboration and mentorship. By sharing a story about a 'zero-productivity' programmer who actually made the whole team better, the author advocates for team-based metrics over individual tracking.
Individual metrics often fail to capture the immense value of developers who act as force multipliers by mentoring others and improving team cohesion.