This is from the "Software Engineering at Google" book, https://abseil.io/resources/swe-book https://abseil.io/resources/swe-book Goals-Signals-Metrics seems l

This is from the "Software Engineering at Google" book, https://abseil.io/resources/swe-book https://abseil.io/resources/swe-book Goals-Signals-Metrics seems like a nice way to organize thinking about performance. Predictive signals or metrics are the grail - lagging signals or metrics don't tell us much about what to do to improve. Maybe it is interesting to compare metrics in the context of engineering centered processes (this) vs product development or product investment processes. The latter is more business focussed, and looks not our efficacy (SWE) but our business impact relative to business expenditure. Maybe that's a question of whether Product Management is sitting in Engineering or not. Are we getting things done well (SWE) or are we building the right things (product). The product POV never not has an impact on dev quality of life.