3 ms·

Also bear in mind: results of software developers are not defined by hours spent coding. > less focused on work gradually in time This might happen. It's a le

• ttoinou 5y ago
  Saying it's the manager's job to deal with that doesn't solve the issue of helping managers deal with that job. The question remains open. I gave a specific example where a manager can't "Keep in touch" because the work was gradually slowed each month, in a way that the manager can't see that time spent declined, he can only think that it's the employee's normal productivity
• md_ 5y ago
  Makes sense. But it's well-known that software delivery estimates have huge error bars. I frankly would have limited insight if a skilled engineer reduced output by 30% in order to work a part-time job. Ultimately, the challenge here is that managers and engineering leads just don't have a great ability to know how expensive a project should be, which is sort of bizarre given that for a lot of software the development costs are the primary costs!
  • egorfine 5y ago
    I strongly believe that software development estimations are futile.
    • md_ 5y ago
      Right, but my point was that if you can't reliably estimate how long something will take, you can't estimate how long it ought to take, and, by extension, can't estimate if it's taking longer than it should. So, as a leader, how do you know if someone is over or underperforming?
      • egorfine 5y ago
        Unfortunately, there is no algorithmic solution to this. It's like porn: hard to define, but you know it when you see it.