Jul 27, 2017 · 1 min read
Good one, Karen! Thanks a lot. There are always both sides of the story: Product Managers should know what makes engineers tick, and engineers should know what ultimately brings value to the company.
In this context, PMs or other roles might find these two links helpful:
- In order to help non-engineers understand refactoring (and the need for it), I provided an analogy of building a house while the requirements change: https://www.tombartel.de/blog/refactoring-for-non-coders/
- Moreover, there are and will probably always be attempts to measure engineers’ productivity. Here is an analogy that demonstrates why lines of code are not a good KPI for that: https://www.tombartel.de/blog/on-bricks-and-code/
