As "tenkeyless" and other compact form factors without a numpad have become fashionable, a small annoyance has become relatively common: getting one's fingers "lost" in the number row while typing long sequences of numbers, which requires to either look down or to move the hand back to the home row, find the homing keys (F and J), and then go back up to continue typing.
While writing text, the fingertips tend to wander about the three center rows of the main alpha block without the index fingers veering too far away, so "resetting" the hands by searching for the homing keys by tact is easy, but the number row is a different matter — the hand has moved further up and it's kinda supposed to stay there, so resetting by searching for the homing keys is rather less convenient (not to say anything of looking down at the keyboard).
I thought that could this be solved by placing a homing bar in one key in the num row itself, to allow the fingertips to find the correct position just by moving the hands a bit to the left or to the right. I juggled the different possibilities, and this is what I came up with:
In principle, there's a case to be made for any of the keys 4 through 8:
- 4 and 7 correspond to the same columns to F and J, respectively.
- 5 and 8 are closer in vertical alignment to F and J, respectively.
- 6 looks balanced(-ish) and is actually a natural limit (think of split keyboards, where 6 is the rightmost key in the left half and 7 is the leftmost in the right half).
I'm quite happy with the results, and plan to keep those two keyboards this way. Heck, if it were for me, this additional homing key would become part of the standard.
The above said may be easier said than done, though — since I use Model F/M keyboards with buckling springs, procuring homing keycaps for this experiment was easy...
... something that won't be such in keyboards of other brands, with non-flat profiles for their keycaps; the new "homing 6" keycap would need to be manufactured specifically (with the added complication of requiring different versions for different national layouts: (6^, 6&, 6&¬, 6/, 6◌̈, Š, etc.) ). In the specific case of MX keyboards with Cherry-profile keycaps, I wonder if simply using a row 2 keycap would do the trick, serving as the wanted limit marker while not being annoyingly different.