The keyboard is the last physical bottleneck between your brain and shipped code
I type tens of thousands of words a week into Claude Code. The keyboard is the last piece of that loop nobody thinks about, and it carries every prompt, every diff, every commit.
Based on the developer hardware and workflow setup used throughout 2025-2026.
The software layer gets all the attention: agents, snippets, shortcuts. None of it matters if the hardware under my fingers is an afterthought.
Most developers will spend weeks configuring Neovim and never once question the keyboard. I did the same for years.
The AI coding loop changed my typing. Prompts, diffs, context docs, commits: the ratio of prose to syntax flipped. I type more words a day than I did writing pure code.
Voice might replace typing eventually. Until it does, the keyboard is the channel between thought and shipped product. A fast one cuts friction I feel across a ten-hour session.
Latency and feel
I want latency imperceptible from keypress to character. Wired, or high-polling-rate wireless. Tactile switches that confirm at the actuation point taught my fingers the threshold. They stopped wasting force. Programmable layers for navigation, symbols and macros compress multi-step actions into muscle memory. Same idea as Raycast snippets. Split ergonomics let my arms rest at shoulder width. No more hunching inward for eight hours.
The setup I use
I type on a Kinesis Advantage. Concave key wells curved to the length of each finger. Columns instead of the staggered offset we inherited from 1878 typewriters. Thumb clusters that move the modifiers onto my strongest digits. Mechanical tactile switches chosen for actuation not sound. Fully programmable. A nav layer that keeps my hands on home row instead of reaching for arrow keys.
Each choice saves fractions of a second. Over hundreds of sessions those become hours. Same idea as shipping fast: the drag is often in the last place I look.
Below the shortcut
Keyboard shortcuts for power users signal you thought about how people use your product. Same applies to my own tools.
When I hit three keys and my full Claude Code prompt expands, that’s a tactile switch at the right force, a firmware layer routing the input, an OS shortcut firing the expansion, an app executing the result. I used to optimise only the top layer.
A keyboard I use 2,000 hours a year is infrastructure. Mine is either speeding me up or slowing me down. I only found out which after I swapped it.