3 ms·

> my job is actually to attend meetings. It's probably not, though - or, at least one of those meetings is the one where you have to showcase/demonstrate what

> my job is actually to attend meetings. It's probably not, though - or, at least one of those meetings is the one where you have to showcase/demonstrate what you "accomplished" in spite of all the interruptions. You do have to produce something in spite of all the time wasted in meetings. I've unironically been told that that's what the weekends are for.

sombremesa 5y ago
The 'my job is actually to attend meetings' was tongue-in-cheek - perhaps that wasn't as obvious as I thought. These days I code during the meetings, since it doesn't seem to make a difference whether I pay attention. > I've unironically been told that that's what the weekends are for. This kind of rings true, I've only been here around 3 months. I did spend a couple of weekends on code in the first month, but overall this company (and my comp) really isn't worth that kind of effort, so I've stopped. I really only joined this company because I wanted a better work life balance (joke's on me) and my business isn't yet profitable, but I'm actually financially independent so it's tough to muster up motivation to work overtime for free.
- ipaddr 5y ago
  Have you ever tried just not showing up. Or pitting two managers against each other? I would love to attend your meeting but this other team needs this. Let them schedule it out for you?
  - gregmac 5y ago
    I went on a kick of replying (and sometimes declining) meetings without agendas, asking "what is the agenda for this?" And sometimes with an agenda, I will try to reply and resolve whatever it was about asynchronously. There have been several meetings avoided when I replied with something like "this sounds like known bug #1234" or "here's the wiki page documenting this: is there something else not covered?". My # meetings went down after I started doing this. Maybe it changed the culture in a good way, or maybe people got tired of me and stopped inviting me to meetings.. but either way seems like success.
    - ithkuil 5y ago
      The threat of a meeting seemed to have worked as intended

sombremesa 5y ago

The 'my job is actually to attend meetings' was tongue-in-cheek - perhaps that wasn't as obvious as I thought. These days I code during the meetings, since it doesn't seem to make a difference whether I pay attention. > I've unironically been told that that's what the weekends are for. This kind of rings true, I've only been here around 3 months. I did spend a couple of weekends on code in the first month, but overall this company (and my comp) really isn't worth that kind of effort, so I've stopped. I really only joined this company because I wanted a better work life balance (joke's on me) and my business isn't yet profitable, but I'm actually financially independent so it's tough to muster up motivation to work overtime for free.

ipaddr 5y ago
Have you ever tried just not showing up. Or pitting two managers against each other? I would love to attend your meeting but this other team needs this. Let them schedule it out for you?
- gregmac 5y ago
  I went on a kick of replying (and sometimes declining) meetings without agendas, asking "what is the agenda for this?" And sometimes with an agenda, I will try to reply and resolve whatever it was about asynchronously. There have been several meetings avoided when I replied with something like "this sounds like known bug #1234" or "here's the wiki page documenting this: is there something else not covered?". My # meetings went down after I started doing this. Maybe it changed the culture in a good way, or maybe people got tired of me and stopped inviting me to meetings.. but either way seems like success.
  - ithkuil 5y ago
    The threat of a meeting seemed to have worked as intended