I have always done my best thinking while walking around or doing something that wouldn't necessarily be considered "work". Cool blog, makes sense to me.
Measuring engineering can be a slippery slope towards stack ranking performance -- which ultimately hurts performance and culture.
I think you have to measure with the intent to improve how your team works. If a manager can measure at the team level and open up visibility into the development process, they can hopefully find where things get frustrating (ex. waiting for someone to review a PR).
That said, there seem to be more mature tools out there than OKAY's beta. There's a discord server called dev interrupted that talks about this stuff a lot.
I just started a community for developers on a discord server and it seems to be scratching the itch for a lot of people. We can only be found by word of mouth, which has it's pros and cons - fewer members but high quality conversation it seems.
So I think there are communities still out there for people, but like the article said, they can be hard to find/know about. But you're welcome to join mine if you're interested in software dev team chat: https://discord.gg/tpkmwM6c3g
I feel like half of my bosses don't understand what goes in to my teams process for new features. They're probably the ones that bought Jira in the first place.