this post was submitted on 05 Nov 2024
32 points (97.1% liked)

Programming

17339 readers
382 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
top 3 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 13 hours ago* (last edited 13 hours ago)

This really reads to me like the perspective of a business major whose only concept of productivity is about what looks good on paper. He seems to think it's a desirable goal for EVERY project to be completed with 0 latency. That's absurd. If every single incoming requirement is a "top priority, this needs to go out as soon as possible" that's a management failure. They either need to ACTUALLY prioritize requirements properly, or they need to bring in more people.

For the Chuck and Patty example, he describes Chuck finishing a task and sending it to Patty for review, and Patty not picking it up because she's "busy." Busy with what? If this task is the higher priority, why is she not switching to it as soon as it's ready? Do either Chuck or Patty not know that this task is the current highest priority? Sounds like management failure. Is there not a system in place (whether automatic or not) for notifying people when high priority tasks are assigned? Also sounds like management failure. Is Patty just incapable of switching tasks within 30-60 minutes? She needs to work on her organization skills, or that management isn't providing sufficient tooling for multitasking.

When a top-priority "this needs to go out ASAP" task is in play on my team, I'm either working on it, or I know it's coming my way soon, and who it's coming from, because my Project Lead has already coordinated that among all of us. Because that's her job.

From the article...

Project A should take around 2 weeks

Project B should take around 2 weeks

That’s 4 weeks to complete them both

But only if they’re done in sequence!

If you try to do them at the same time, with the same team, don’t be surprised if it ends up taking 6 weeks!

Nonsense. If these are both top priorities, and the team has proper leadership, (and the 2 week estimate is actually accurate) 4 weeks is entirely achievable. If these are not top priorities, and the team has other work as well, then yeah, no shit it might be 6 weeks. You can't just ignore the 2 weeks from Project C if it's prioritized similarly to A and B. If A and B NEED to go out in 4 weeks, then prioritize them higher, and coordinate your team to make that happen.

[–] [email protected] 1 points 1 day ago

Except UI changes. Those should just stay in progress forever.

[–] [email protected] 1 points 1 day ago

I appreciate this. It’s a good overview of what it means to be a productive part of a larger context.

I prefer the terms “throughput” for “worker productivity” and “latency” for “work-unit productivity” but I can see why they chose to use their terms.