this post was submitted on 08 Jun 2024
720 points (97.0% liked)

Programmer Humor

32360 readers
854 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 4 months ago (3 children)

Why not reach out to reach to each team member on a daily or semi daily basis to ask that question?

These meetings REALLY get in the way of progress and we've been killing it ever since our new manager started doing it like this

[–] [email protected] 4 points 4 months ago (1 children)

I really don’t understand how a 5-10 minute meeting can get in the way of progress

[–] [email protected] 1 points 4 months ago* (last edited 4 months ago)

primarily because both context switching and progress builds upon itself so stopping & switching has more impact than those 5 or 10 minutes suggests. (ie. you can stop a car from rolling down the hill with just one finger if you do it early enough but in reverse).

also standup meetings have a way of getting longer and covering more ground that what was initially planned for. (ie meeting mission creep)

[–] [email protected] 1 points 4 months ago

When I worked as a PM that's what I used to do - daily check in about any obstacles that I could clear. Took me a little while to get around everyone but it didn't waste everyone's time

[–] [email protected] 10 points 4 months ago* (last edited 4 months ago)

I actually tried a daily slack bot instead. The team HATED it with a passion. And the amount of productivity lost on other teams to a backend engineer blocking a systems designer being blocked by a UX flow etc is insanely large. We have never missed a deadline, hit all our revenue targets, and get much. much larger features done in 2/3rds of the time of the next nearest team. Part of that is because we've made sure to reinforce the concept that we are a single team instead of a group of server engineers, backened engineers, frontend engineers, system designers, [removed to protect identity] designers, econ specialists, UX designers, UI artists, and QA working in their own bubble.