3 ms·
In this case you're choosing to be unproductive. If you're able to spend time on HN and reply during a meeting you could just as easily be fixing the root cause
by ckdarby 6y ago
In this case you're choosing to be unproductive. If you're able to spend time on HN and reply during a meeting you could just as easily be fixing the root cause of development tools failing.
Protect your time, block out your calendar, and fix the root causes that create the unproductive meetings.
- qz2 6y agoI'm doing that too. I am waiting for Vagrant to install Windows :)
- majewsky 6y ago> fix the root causes that create the unproductive meetings BRB, fixing the org chart. /s
- oneplane 6y agoUnironically, this is what we did. Removed all 'layering', practically making groups of either product or tech and only 'manager' layer between that and C-level. Manager is only allowed to deal with people-stuff and PO's are only allowed to deal with product stuff. Everything else is up to the teams. Works pretty well for us! (and 'allowed' doesn't mean as a hard rule, it's just not their focus point, same goes for product vs. tech, it's not that you are walled off or something, it just means your core is very clear and how far away from that core you can get depends on your team and needs)
- tubularhells 6y agoI'm not paid twice for working during meetings, so I don't work during meetings.