4 ms·

Today I showed up at 9:06 and was told to go home for the day, and to come back on time on Monday. Get a new job. If what you say is true, and you can find wo

Today I showed up at 9:06 and was told to go home for the day, and to come back on time on Monday. Get a new job. If what you say is true, and you can find work elsewhere, do so. If they're silly enough to throw away 7 hours of productivity over a 6 minute delay, fuck'em. For a customer-facing position, your happy ass should be in a seat and smiling fifteen minutes before the client shows up. For development work, though, especially if you aren't coordinating with other people, you should be able to focus on producing quality work quickly. The time fetishism I've seen is something I mostly see in folks older than their 30s--basically, they don't get that time isn't the big factor it used to be, especially for developers.

shortstuffsushi 11y ago
Yes and no. Sending them home for being 6 minutes late is totally overkill (unless it's something that has occurred many times, and there have been warnings). Quitting for being sent home for a day also seems like an extreme reaction, though, especially if you like the job otherwise. I wouldn't call it time-fetishism, and I wouldn't say it's something limited to "older folks," that seems particularly unfair. I'm 24, and when people couldn't be bothered to show up on time, I was bothered by it as well. And I'm a developer. I know that it's not vital that "you be in by x-o-clock or no work will be done for the day," but it definitely creates a stigma toward the individual who roles in later than the rest of the team.
- angersock 11y ago
  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.

shortstuffsushi 11y ago

Yes and no. Sending them home for being 6 minutes late is totally overkill (unless it's something that has occurred many times, and there have been warnings). Quitting for being sent home for a day also seems like an extreme reaction, though, especially if you like the job otherwise. I wouldn't call it time-fetishism, and I wouldn't say it's something limited to "older folks," that seems particularly unfair. I'm 24, and when people couldn't be bothered to show up on time, I was bothered by it as well. And I'm a developer. I know that it's not vital that "you be in by x-o-clock or no work will be done for the day," but it definitely creates a stigma toward the individual who roles in later than the rest of the team.

angersock 11y ago
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.