3 ms·
The point about remote workers been less efficient.... I really do hope they accounted that they were probably not shown the ways to game the "efficiency" syste
by roomey 4y ago
The point about remote workers been less efficient.... I really do hope they accounted that they were probably not shown the ways to game the "efficiency" system.. most people won't tell a new worker who they never met how to do something like game the efficiency metric.
Although and manager worth their salt would know to pass this info along.
And anyway, in a "creative" area, like writing code, inventing new stuff, since when is "efficiency" a good thing, all that does is make the same shot, just more of it.
"Year of efficiency" is year of cost cutting. The blog post has an interesting take on it tho.
- wg0 4y agoEfficiency is meaningful in manufacturing where you exactly know what goes into a shoe, how many steps, processes and how much energy and material goes into each. You're making the same thing over and over. Then there, it's justified to say that 100 shoes per minute is better than 96 shoes per minute and additional 4 shoes can be considered as additional revenue or bringing average cost down etc. In software, the same thing with the same software stack with the same code base is not happening. If it's happening, either the activity is meaningless or can be a step in the build pipeline as requires no thought. Efficiency can be measured either on number of bux fixes, features added or lines of code. Great. Lines of code are meaningless they even vary by software stack, language, framewok, domain, Feature scope or bug's severity. Bug fixes have exactly the same problem. Could be two weeks to find out that the issue isn't even in the code but in an external that had an incorrect value. Features? Don't know. How much against the existing features the new features goes? The more that slope is, more necessary refactoring would be required.