If it really bothers you, every time you realise you did this, delete the previous word before the F and retype it, maybe even a few times, while paying attention to every movement. Slowing down helps too.
Mine is ctrl+shift+s, because it saves an incremental version. This way, if the client says "Actually I preferred the bassline an hour ago, can we go back?" I can say "sure, no problem!".
It also protects in case the file is corrupted. I know so many people who just save over the same file and it always amazes me.
Whatever app you're using, check the shortcuts list and see if there's one for incremental save... it may just save you from losing many hours of work one day! Once your brain gets over the hump of adjusting the ctrl+s reflex, of course :)
Once after a particularly long and gruelling session, I tried to ctrl+shift+s a film I was watching haha.
This is wild I picked up this quirk like 4 years ago, F key even. I code so a lot of the times I'm already ending something with a semicolon, but then the line gets an extra temporary F just to be sure