Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Voxera115854yThat usually mean one of two things.
Either you where sleeping which indicates it was a meeting you probably did not need to attend.
Or the meeting was meaningless altogether and should never have been started.
A good meeting must be relevant, should be interesting and only as long as required, break early if done. -
I’d say any meeting above half an hour needs pauses every 30 min. Oh, and short recaps after them!
Can you power through it? Yes! Should you? Nope.
Edit: I also had a shorty meeting like that. Spent 2 hours trying to go over our definition of done cause adding a “testing” column in our jira was too big brain for the other devs and the manager, so better discuss for two hours if we should keep tasks in progress and not undrestand if they are done but testing or keep them in done but they are not really done and still testing.
The justification for not doing it? “But what about the board on the wall? It’s too small, we can’t have the column there and we can’t have it differ from jira!”
I don’t know how I didn’t punch anyone’s face at that statement. -
Voxera115854y@piratefox ditch the board and add a big screen.
But I guess that would require a month long meeting to say no to :/ -
Meetings are like 1 to n where only one person need to be in all the time and the rest should be in a meeting for a fraction of the time.
6 hours of meetings and I can't remember a damn thing of what was discussed.
rant