I’m simultaneously trying to get my fingers used to two keyboards: the Keyboardio Model 01, and the OLKB Preonic.

There are probably cheaper ways of introducing hordes of errant keypresses into your daily work.

They’re interesting keyboards. Perhaps the most striking thing they both have in common is how they reduce the space bar to a normal sized key, allowing your thumb access to a lot more keys.

So, on the current preonic keymap, my thumbs are responsible for the space, delete, enter, shift, command and mode-shift keys. It makes for a compact keyboard, but… it’s probably too much. I thought it’d be a good idea to combine my shift and enter keys, for example (hold down the key and press another key for shift behaviour; just tap the key for enter). I also have that key right beside my space key. Now what happens is that I press enter all the time instead of space. In apps like Slack, where enter starts a new message, that leads to very disjointed and confusing conversations. With your boss. Who might be wondering if you’re drunk.

However, the neat thing about both keyboards is how you can re-program them to behave almost however you’d like. I think I’m going to break the shift/enter key combo, instead taking a leaf from the default Model 01 layout and combing the enter and space keys instead (tap for space, mode + tap for enter). I’ll post back here after some experience with that.

Other notes:

• the ortholinear layout (unlike the staggered keys layout on traditional keyboards) took me no time at all to adjust to. I touch type and don’t even notice the difference.
• I’ve yet to find a good use for the latching key-switches I added (tap ‘em once to lock them down, tap again to unlock) but I’m still thinking about that
• typing on heavy clicky mechanical switches (Kailh Box Navy type) is very pleasant but definitely more tiring, and possibly slower too, compared to shallow travel keyboards that bottom out near immediately
• My keycap set hasn’t enough accent keys, and using words for keys like “alt” means you can’t turn them 180º for easier typing by thumb. It’s the MDA-profile Big Bang 2.0 set - gorgeous otherwise. Despite the mis-sized “8” keycap legend.
• The current QMK instructions for updating your keyboard layout are right, but not the easiest way to do it - instead, just use the online configuration tool; it’ll compile your firmware for you too!

The Pimoroni Keybow is a great little 12-key macro-pad kit. I got mine with Kailh Gold clicky keys too, as I wanted to see what those were like - they’re nice, light to press but with a definite click. They come with a DSA keycap profile too. I’m currently fascinated by keycap profiles and I really want to build a keyboard with high-quality SA keycaps and heavy clicky keys to emulate the look and feel (if not noise!) of the beam-spring behemoths of yore - but that’s a topic for another day.

Back to the Keybow kit. You can make it without any tools and it gives you a RaspberryPi-powered macropad - a small but fully-fledged computer that you can configure to your heart’s content, if you’re comfortable digging into configuration files and maybe some light programming.

Even if you’re not, you can still do some fun things! Each key has an RGB LED under it, and Pimoroni have set it up so that you can animate the LEDs just using an image file in PNG format. Any popular image-editing tool can create these. The image file should be 12 pixels wide, one for each LED, and you can animate it by having additional rows. One row is a single step in the animation (so just have a single row for a static set of lights permanently on).

It’s not clear from the Keybow’s documentation which column in the image corresponds to which key. It doesn’t match how the keys are numbered in the programming sections. After some experimentation, if you orient the keybow so that the USB cable is coming out of the top, column one of the image is on the bottom left, the bottom right is column four in the image, the top left is column nine, and the top right is column twelve. The two keys in the middle row are columns five and six of the image, and so on.

With that worked out, I wanted to make a snow animation, matching the orientation of the keys (i.e. with the narrow side facing up). The image file I made is here. It’s not quite as random/unpredictable as I’d like, but a few more animation cycles would help - pull requests welcome :)