[ilinx]

My rule of thumb is that if you’re not measuring anything you’re not engineering. It’s not the whole picture, but to me the engineering part sometimes means being able to explain (and even quantify) why one solution is better than another.

[ndriscoll]

I've found coding assistants to be a huge boon for this. All of the thorough analysis that previously would've taken a bunch of tedious extra thought work to do for marginal benefit (with a well-calibrated intuition) becomes 5 seconds of thought to the the computer to build a harness and then letting it chew on that for 15 minutes. It now also takes me one command and less than a minute to get pprof captures from all the production services my team owns (thanks to some scripts I had it write), which is just something I never would've bothered to automate otherwise, so we never really looked much at it. Codex is also very good at analyzing the results, and finding easy wins vs. knowing what would be invasive to improve, and then just doing it.

Thinking of seeing if I can get mutation testing set up next, and expanding our use of fuzzing. All of these techniques that I know about but haven't had the time to do are suddenly more feasible to invest into.