4 ms·
No one wants to work for those companies, either. In software engineering, the only metric needed to gauge performance is to track PRs and tickets. We have a
by DarknessFalls 4y ago
No one wants to work for those companies, either. In software engineering, the only metric needed to gauge performance is to track PRs and tickets. We have a bi-weekly sprint velocity that tells managers how we're performing.
Only lousy workers are going to put up with having hours wasted on "cake day" and forced water cooler discussions.
- PraetorianGourd 4y agoBut that just is not true. A very small team with a very focused codebase perhaps. But when you are balancing 40 competing issues that are impacting a wide range of cusromers, where each issue has the potential for downstream impact on all of the other issues it isn’t just PRs and tickets. Combine this reality with the fact that your team not only needs to deliver bugfix X for customer Y, but also needs to work with the other team delivering feature Z for customer A, which shares code with bigfix X. Things quickly evolve beyond independent fiefdoms.