Not necessarily so I can work less (afterall there is always work to do as a developer). But so I don't get annoyed.
Usually that ends up saving time for the company, but not always.
Not necessarily so I can work less (afterall there is always work to do as a developer). But so I don't get annoyed.
Usually that ends up saving time for the company, but not always.
On a ROI and prioritization metrics I put myself first, co-workers second, product third, company bottom-line fourth. Part of putting myself first is delivering things mandated by management (so, you know, I don't get fired) which skews to product and company bottom-line, but things I do of my own volition is definitely not going to the bottom-line/product.
I am lucky I am not time tracked aggressively and that my immediate superior lets us work on things out of our own volition. The fact that some of the stuff I do benefits the company indirectly is secondary to my motivation to do it.