Using workman layout for 1 year. Retrospective.

<-Back

Table of Contents

1. Preface

Using QWERTY on a regular basis was never an option to me. It has a lot of frequently used key far from standard position, high index of a Same Finger Utilisation, slow average speed of typing common bigrams etc1.

But this article is not be about pros and cons of workman, but about the state of its ecosystem and the pitfalls I falled into for the last year.

2. Experience

2.1. Editors

I'm a fan of vim-keybindings and I utilize them heavily everywhere I can: emacs with evil-mode, qutebrowser, firefox with a vim extension.

hgkl is undoubtedly the most oftenly used keys, and in workman they correspond to neoi. After installing a brand new vim-driven thing, the first thing you will have to do is to substitute hgkl bindings, as the navigation without them is absolutely painful at best. Hence, the next big step is to ensure that you've changed every hgkl binding for every environment/mode.

And the most challenging thing is to find all of them in this beautiful piece of software you see for the first time in your life. Believe me, looking up "n" in a 1k lines long file is not how you want to spend your evening.

Luckily, there are plugins which alter default keybindings, such as keyboard-layout2 for spacemacs and workman-vim for vim3, 4

So the point is that whenever you acquire something which relies on the position of keys regarding each other, you'll have to dedicate some extra time to tune the thing up as it'll be pretty unusable at the beginning.

2.2. MacOS

Changing default system layout is also a bit complicated, brace yourself for some tricks with configs juggling5, 6.

2.3. Typing on your friend's laptop

I never use any other layout, except worman, on my machine, so it's fairly impossible to blind-type anything in qwerty, but since I use qwerty on my phone, the performance is pretty decent, not poor I'd say. It's just that I cannot type without looking at keyboard.

Footnotes: