3 ms·

Teams where it's a stigma, especially when we all know that time is fluid and productivity varies widely, even in spite of product shipped are bullshit and are

Teams where it's a stigma, especially when we all know that time is fluid and productivity varies widely, even in spite of product shipped are bullshit and are getting eaten, slowly but surely, by flexible companies, remote workers, and Stuff-as-a-Service. Burn your timesheet, and focus on shipping. EDIT: There's literally no good reason, if you aren't facing customers, to sweat time variations, especially if doing so comes at the cost of developer productivity. Just because somebody is used to a bullshit time system tracing directly back to the factory shifts of yore doesn't mean that more enlightened folks should stick with it when better options are available.

shortstuffsushi 11y ago
I'm not arguing for time sheets, or even any form of time tracking. Just that as a team, if we agree to show up to the office at a time, and someone isn't there then, you'll have feelings about it. The part about teams that operate via timesheet is a bit of a stretch, imo. At least in larger orgs, I don't see the "need" (read: keeping middle-managers employed) for time tracking ever going away. While I agree with the sentiment that time tracking is pretty useless, I don't think it's going to stop.