Software unrationalized
Over a year ago I wrote this post showing how and why Lukacs' predictions for labor under capitalism fall short in the case of software engineering.
This article, which sort of confirms the point, just found its way to my inbox from our very-very-recently hired Director of Business development, who will be my boss for part of my time. It's about how Meetup.com radicalized their management structure to allow greater employee autonomy.
What brought about the change was impracticality of having a fully rationalized work force in a software development environment. They coined a word for this problem:
Employees talked about being "metrified," or so focused on metrics there was no room for new ideas.
Baby steps, sure. But I think it's progress.
This article, which sort of confirms the point, just found its way to my inbox from our very-very-recently hired Director of Business development, who will be my boss for part of my time. It's about how Meetup.com radicalized their management structure to allow greater employee autonomy.
What brought about the change was impracticality of having a fully rationalized work force in a software development environment. They coined a word for this problem:
Employees talked about being "metrified," or so focused on metrics there was no room for new ideas.
Baby steps, sure. But I think it's progress.