TapNoiseTyping speed can be interesting feedback, but it is a poor general target for knowledge work. Thinking, reading, revising and reviewing can all be useful while producing few key presses.
Separate practice from production
A typing exercise has a defined passage and an accuracy rule. Everyday work often has neither. A fast burst of familiar text is not directly comparable to composing an argument or debugging a difficult case.
If you want to practise, use a bounded session and track accuracy with the speed. Do not compare a background WPM estimate with a timed test as though both measured the same thing.
Treat counts as counts
TapNoise records local activity and progression, not the quality of your writing or code. Its live speed estimate uses key positions and does not read the resulting words to judge correctness.
A streak or hat can be playful. It should not become a reason to type filler, press harder or postpone a break. Hide the buddy or stop checking the stats if the number is steering you away from the task.
Choose a better session outcome
Define the result you want to leave behind: a revised page, an answered question or a verified fix. Check that result when the session ends.
For the calculation itself, see how WPM is estimated. For a healthier reminder habit, choose an interval you will respect and stop when you need a pause.
Sources: TapNoise local statistics, Tappy progression.