3 ms·

Or use the metrics to spot check your processes, and move on to other concerns before the histamine reaction starts. In theory you can return to the metrics la

• osigurdson 2y ago
  What are some example metrics that you might track that add value?
  • hinkley 2y ago
    With any new habit in life, you fixate on it for a very brief period and then try to let it fade into the background. Then you periodically revisit it to see how you’re doing. From a programming standpoint, and off the top of my head, I would include TDD, code coverage, and anything that comes out of a root cause analysis. I tell junior devs who ask to spend a little more time on every task than they think necessary, trying to raise their game. When doing a simple task you should practice all of your best intentions and new intentions to build the muscle memory.
    • osigurdson 2y ago
      >> TDD, code coverage I don't know how to track TDD, but for me, code coverage is an example of the same old false proxies that people used to track in the 000s. Before creating a metric and policing it, make sure you can rigorously defend its relationship to NPV. If you can't do this, find something else to track.
• alok-g 2y ago
  Why not define additional metrics around what you would spot check and then produce a consolidated figure of merit as the metric to optimize. Aren't we doing that with AI training and general optimization (including regularization).