I suppose it's my typing style then. I'm not a touch typist although I can keep up with anyone who's not seriously trained in touch typing. (I don't look at the keyboard f.ex.)

At any rate I will continue to use underscores unless the   is somehow visualized. Cause how do you want to distinguish a list function chain like @this from a spacified long funcname like @this? (View source and you'll see I typed the latter with  s.)

It can't be the reaching for Shift that breaks your flow - you need to reach for that one for the caps too. So it's the awkward position of the underscore. Obviously the real solution then is to use any kind of real editor and map the underscore to an additional key. Assuming you have mapped Ctrl to Where God Intended It To Be (who ever needs Caps Lock?), Ctrl-Space should work beautifully.

Yes, it does lengthen identifiers - but I'd rather type long identifiers. The other option would be to squint my eyes at the embedded caps until I decide to turn up the font size.. eh..

Makeshifts last the longest.