Real programmers measure their output in SPMs: saves-per-minute 😂

At least when fixing/improving code, I find a really good measure to be change of total wtf in the code per time spent working.

Total wtf is user wtfs plus wtfs while reading the code, or trying to make it do something that "should be simple".

Reducing user wtf/m quickly means you're effective at targeting the most important wtfs first, but the total is a more sustainable metric because it discourages silly things in code to quick-fix user-side issues.

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!