4 ms·
> code written, keystrokes, mouse movements, sleep/work schedule, productivity metrics, etc That's not the most valuable info at all. What would be valuable i
by 908B64B197 5y ago
> code written, keystrokes, mouse movements, sleep/work schedule, productivity metrics, etc
That's not the most valuable info at all.
What would be valuable is to know which ecosystem, languages and tech people are investing time and resources into. These are the ones you need to prioritize for your dev tools. For instance, Microsoft decided to invest in supporting Rust https://docs.microsoft.com/en-us/windows/dev-environment/rust/rust-for-windows https://docs.microsoft.com/en-us/windows/dev-environment/rus... as well as making sure .NET works on all OS.
> or build a productivity dashboard so managers can fire people for not being productive enough (like Xsolla did)
When a competitor decides to start using these, it's awesome. You get a nice window of opportunity to poach high performers.