3 ms·
As a technical manager, this actually isn't that far from what happens with teams of engineers. The less precise I am in describing the requirements of a system
by mondoshawan 10y ago
As a technical manager, this actually isn't that far from what happens with teams of engineers. The less precise I am in describing the requirements of a system, the less correct solution is produced. This isn't to say that my team is incompetent or mindless -- far from it, I find them to be some of the most talented engineers I've had the pleasure of working with.
Perhaps the solution to this particular problem is a clear specification of the requirements of the problem -- very similar to how corps define requirements documents for what their product does/behaves like?
- qw 10y agoI'm not saying it applies to your case, but one danger of specifying a problem in too much detail, is that it teaches the engineers to think less about the problem. From my experience developers often think of failure cases that the managers are not aware of, or have a simpler solution to a problem.
- NegativeK 10y agoAnd yet if the problem isn't specified enough, we engineers will run off and deal with failure cases that aren't relevant to the client's needs.
- prance 10y agoThis discussion reminds of this question/answer on quora: https://www.quora.com/Since-programming-can-be-self-taught-why-not-major-in-something-other-than-computer-science/answer/Jayesh-Lalwani?srid=us6J7 https://www.quora.com/Since-programming-can-be-self-taught-w...
- mondoshawan 10y agoI, too, find this to be the case. There seems to be a happy medium of "you figure it out" and "it must do exactly this". As a relatively new manager, I find figuring out where the balance is tricky.