5 ms·

I like the idea of "breakfastable offenses." I'm curious if you had remote teammates. If so, was there a workaround? It reminds me of my SCUBA training. The

I like the idea of "breakfastable offenses." I'm curious if you had remote teammates. If so, was there a workaround? It reminds me of my SCUBA training. The head instructor had a list of offenses. If you committed an offense (i.e. leaving goggles on forehead after surfacing), he'd say, "6-pack," obligating you to bring a 6-pack of beer. ;-)

vollmond 11y ago
We had no remote teammates. Not sure how we would have handled that :-) Some of the other offenses: * Breaking the build (unit tests only) and then leaving for the day without fixing it or reverting your change * Walking away without logging out of your machine (very security-conscious business) * Not completing an assigned code review within a week of being assigned (within reason -- if the code review was enormous, or you were overly busy with an enormous project of your own, don't worry about it)
- csours 11y ago
  If I see an open machine I write an email from them to their manager saying "remind me to lock my machine before walking away".
  - facetube 11y ago
    Probably unwise. "What else did he/she do?" types of questions come to mind. Probably depends heavily on where you're working, though.
    - csours 11y ago
      A little paranoia can be a good thing.
  - vollmond 11y ago
    That was how we generally accomplished that enforcement -- see an unlocked machine, write an email to the team list saying "I'm bringing breakfast tomorrow!"
  - elssar 11y ago
    At a previous company, we had a culture of sending out prank emails from open machines. I once sent out an email from a co-founders account which said that he was fed up with the crappy codebase and was hiring a new team to rewrite it from scratch and that the other (non-tech) co-founder was to take over the existing tech team. No one took it seriously (non-tech co-founder helped me draft the email, the other one laughed while reading it after the fact), but there was a board member in the mailing group who thought it was serious and started sending panicky emails to the co-founders.

vollmond 11y ago

We had no remote teammates. Not sure how we would have handled that :-) Some of the other offenses: * Breaking the build (unit tests only) and then leaving for the day without fixing it or reverting your change * Walking away without logging out of your machine (very security-conscious business) * Not completing an assigned code review within a week of being assigned (within reason -- if the code review was enormous, or you were overly busy with an enormous project of your own, don't worry about it)

csours 11y ago
If I see an open machine I write an email from them to their manager saying "remind me to lock my machine before walking away".
- facetube 11y ago
  Probably unwise. "What else did he/she do?" types of questions come to mind. Probably depends heavily on where you're working, though.
  - csours 11y ago
    A little paranoia can be a good thing.
- vollmond 11y ago
  That was how we generally accomplished that enforcement -- see an unlocked machine, write an email to the team list saying "I'm bringing breakfast tomorrow!"
- elssar 11y ago
  At a previous company, we had a culture of sending out prank emails from open machines. I once sent out an email from a co-founders account which said that he was fed up with the crappy codebase and was hiring a new team to rewrite it from scratch and that the other (non-tech) co-founder was to take over the existing tech team. No one took it seriously (non-tech co-founder helped me draft the email, the other one laughed while reading it after the fact), but there was a board member in the mailing group who thought it was serious and started sending panicky emails to the co-founders.