3 ms·
As to what one should track, one should track _results_ if you've managed to accomplish something useful with very little code, that is decidedly better than ac
by 0xbear 9y ago
As to what one should track, one should track _results_ if you've managed to accomplish something useful with very little code, that is decidedly better than accomplishing the same with much more code and hundreds of check-ins. Simplicity is the ultimate sophistication.
- Swizec 9y ago> one should track _results_ One should, but companies often care more about effort than results. They can manage based on effort, they can't manage based on results. If you spend 2 days getting the same results as somebody else does in 5 days, guess what, they don't want you milling around those extra 3 days and bringing morale down. Gotta give you more work!
- thanksgiving 9y agoWell at that point I think you've hit the agency problem where management's goals and the organization's goals are different. The organization's goal is delivering results but that is not necessarily what management wants right now.
- 0xbear 9y agoAnd worse: in more than one megacorp (including Google in late aughts) I've seen _complexity_ as a requirement for promotion. Google has tried to get rid of that de jure, but it remains a requirement in practice, so people do what they are rewarded for: create complexity.