Going split

I had been wanting to go fully split for quite some time, especially after designing the Array54 and later the Node40 (which is still not quite done).
So I thought to myself: why shouldn’t I build an ergonomic split keyboard for myself?

I’d had my eye on the Dactyl Cygnus for a while—it really captured my imagination—and I was already aware of the clear benefits of a more ergonomic keyboard.
So why the Dactyl Cygnus? It’s more aesthetically pleasing than a regular Dactyl-style keyboard, and it comes in several configurations, so I decided to give it a try.

As luck would have it, a friend of mine had one he wasn’t using and offered to lend it to me.

The struggle

At the beginning, I had quite a bit of trouble using it. After many years of incorrectly using a row-staggered keyboard, I had learned to touch type (albeit imperfectly) fairly efficiently—but at the cost of wrist pain and poor posture.
I tend to angle my wrists inward, and naturally, my arms and shoulders followed.

The first challenge was simply placing my hands correctly on the halves. After some time (and switching to a keycap set with legends), it started to feel more natural. My fingers began to land on their intended columns.

The next issue was the thumbs. Previously, they had one sole responsibility: the spacebar. That was no longer the case—now each thumb had access to three keys.

This is where I hit the next hurdle: muscle memory.
Believe it or not, this was the hardest part to overcome—unlearning the habit of moving my hands across columns not assigned to each finger.

For some, this might come naturally. For me, it meant actively fighting what had become instinct after years behind a computer screen. The key, in the end, was dedication.

I’m not going to pretend the switch was easy. I still had a row-staggered keyboard nearby that I fell back to frequently in the beginning.
But the more I used the split keyboard, the more I began to notice its real benefits—and the easier it became to look past the initial drop in productivity.

Needless to say, I used my old keyboard less and less.

At one point, I was even ready to give up. I went from not having to look at the keyboard at all to struggling with basic sentences.

The rewards

After some initial trouble with the keymap and firmware (KMK), I eventually got QMK with Vial running on the MCUs. That opened up much more freedom to reconfigure the layout in real time.

Then one day after work, I noticed something: my wrists and shoulders didn’t hurt as much as they used to.

My posture improved as well. I stopped collapsing into my chair like a human beanbag and started sitting more upright. I no longer pulled my shoulders inward, and as I became more accustomed to the keyboard, I also became more efficient.

At some point, it stopped feeling like a chore to type—and became something I genuinely enjoyed.

So to sum up the benefits:

  • My chest opened up more, and I didn’t feel as fatigued.
  • I could naturally spread my arms apart.
  • The tension in my upper back disappeared.
  • My wrists now rest in a much more natural position.

As for productivity, it eventually returned to normal—even though I’m still refining my keymap and layers. The difference is that typing now feels more natural.

Key takeaways

  • Keymapping is incredibly important and should be tailored to you.
  • Letting the thumbs take on more responsibility was a challenge. I still make mistakes, but the strain on my pinkies is significantly lower.
  • Posture matters - a lot. Having the right keyboard setup is crucial when you spend 8+ hours a day at a screen.
  • Typing becomes more natural once your muscle memory is retrained.
  • I’ve become more aware of inefficient habits, especially how I used my pinkies.

The reality

  • The learning curve is real. If you’re used to a regular keyboard, expect to relearn how to type properly.
  • Not great for gaming - but for everything else (so far), it’s been excellent.
  • You may need to try several keyboards before finding the right one.

Why I Stayed

We spend so much time optimizing how our tools work, but rarely how we work with them.

I didn’t switch because I was in pain. I switched because I was curious.
But I stayed—because everything else started to feel wrong.