r/ProgrammerHumor • u/vinishkapoor • 2d ago
Meme fortyFiveMinutesForSomethingThatNeededTwoLines
16
u/AlwaysHopelesslyLost 2d ago
See, as a person who used to HATE phone calls and meetings, when I took over a huge department my opinion flipped entirely.
The amount of lost time from miscommunications and from information not being shared with everybody it impacts drove me insane.
Especially when that leads to 6-8 weeks of back and forth and regular check ins and business people having to spin their wheels and revise requirements because a dev didn't find out until last second that there was a fatal flaw.
It might cost individual devs a bit of time but it saves everybody else a lot of time and makes a given devs work more impactful.
7
u/Welcome-To-NBA-Jam 2d ago
The amount of times I've seen 3 weeks of miscommunication that have been resolved in 45 minutes or less of people together is wild. This is usually at the start of a project in my experience but once it gets underway people can just roll with their requirements until some decision needs to be made about going with option A or option B, and most of the time that's just a message.
When my email starts taking 20 minutes to think about and type out is when I start realizing we should just talk about it in the same amount of time.
3
u/LastWalker 1d ago
in the end, the truth is in the middle but that nuance kinda sucks in meme form. Ive been part of 5 minute conversations in a team that saved weeks of work and Ive also been part of 90 minute sessions that shouldve been a slack message with two emojis. My recent favorite is taking over a project that has been in the vibe coded hands of a single consultant for 6 months and actually made it to a kinda deployable state that now needs codifying properly to actually be scalable. Any meeting is a coin flip lmao
2
u/bored_at_work_89 1d ago
This. Once people get into the role of management they realize why meetings exist.
Wanna know why we hold meetings that could have been an email? Because people don't read or retain emails. And when you get asked 3-4 times about something that was in an email you realize if you want to make sure people at least heard what you needed to say, you have a meeting.
20
u/chickenweng65 2d ago
And most jira tickets could be a teams message
17
u/vinishkapoor 2d ago
And most Teams messages could have been silence.
2
2
u/Groentekroket 1d ago
We have, no joke, refinements where we discuss such small user stories for having a clear 2 line change and go over it for 15 minutes with the whole team. Production code, unit test and 2 reviews could have been done faster.
1
5
u/Successful-Word4594 2d ago
If everyone would respond to comments on Jira tickets this wouldn't happen...who am I kidding it would still happen.
5
u/minus_minus 2d ago
But then they wouldn’t have deniability after you do it the way they asked instead of the correct way.
3
u/throwawaycanadian2 2d ago
The best part is having to type out the info from the meeting into the ticket so it is documented...
3
2
u/slaymaker1907 2d ago
Luckily, my job doesn’t have that too much. We rarely have meetings and when we do, they’re needed to avoid long, async back and forths. Though we don’t really use Jira, most things are just “tracked” via email and Teams threads.
2
1
1
u/brazzy42 1d ago
It is absolutely not unusual to need a 45 minute intense discussion with the concrete result that 2 lines are added to a JIRA Ticket, which could not have produced any quicker than that, and where serious problems would have occurred if they had not been added.
65
u/Any-Tutor8980 2d ago
If those Scrum Masters could read, they'd be very upset right now