<p>What do we do differently with the measurement of software work? What do we do if we want to not become victims to whatever foolish analysis is able to game this & use the right keywords or a scary N size to get VCs to amplify every message? </p><p>I have some thoughts and they were forged in the fires of working with students with significant missing data, of working with data on learning outcomes at scale, and of working in contexts where careful work gets screamed at and bullshit gets a promotion</p>
