4 ms·

How does wasting 60 minutes in a meeting cancel out 2 minutes saved elsewhere? I'm not sure I follow that logic. You still got 2 more minutes of labor from that

• brudgers 14y ago
  Where did sixty minutes come from? What happens in organizations is that progress is made in quantum steps, not continuously. As you go higher up in the organization, the quantum is a larger period of time and two minutes of programmer efficiency per day never moves the shipping date forward or changes the feature set. The only real tipping point from a management perspective is if the improved efficiency eliminates a full time employee.
  • greggman 14y ago
    Sorry, 60 minutes was my personal thinking of "programmers attend a meeting". I'm still not sure I see your point. You can pay programmers $1-$2 a minute to do nothing or you can pay them to do something you need done. If you get them a slow machine such that 10-30 minutes a day they are sitting around waiting for a compile, link, or other long build step you're paying them to sit around. Seems like a waste of money. If you can reduce that 10-30 minutes day just a few minutes (say 8 to 24 mintes a day) at least some of those minutes you're already paying for are actually going toward what you want them to go toward (work)