Blog

Mechanical keyboard for programming: what to look for

By | Published

For programming, a good mechanical keyboard is one that lets you type braces, brackets and slashes without finger gymnastics, fits how you use the F keys and arrows, and doesn't bother the person sitting next to you. RGB and brand come later. If we had to boil it down to one idea: when you code, layout matters more than the switch.

1. Layout: what you notice most in code

On the Windows Spanish (Spain) layout, nearly every symbol you use daily in code needs AltGr. Microsoft's own layout tables confirm it: braces, brackets, backslash, pipe, at sign and hash all take AltGr plus another key. On the US layout, brackets and backslash have their own keys and the rest come with Shift.

Symbol Where it shows up Spanish (Spain) US / US-International
{ } Blocks in JavaScript, C, Java, CSS AltGr + ´ / AltGr + Ç Shift + [ / Shift + ]
[ ] Arrays, indexes, lists AltGr + ` / AltGr + + Own key
\ Escapes, Windows paths AltGr + º Own key
| Shell pipes, OR operator AltGr + 1 Shift + \
# Comments in Python and shell AltGr + 3 Shift + 3
@ Decorators, email addresses AltGr + 2 Shift + 2

This isn't just our pet peeve. Developer Hadi Hariri wrote on his blog back in 2009 that he ended up building his own variant of the Spanish layout because braces and brackets were awkward for writing C#. HYTE's ANSI vs ISO guide also notes that many programmers prefer ANSI precisely because of where those symbols sit.

The catch for anyone who also writes in Spanish is Ñ and accents. Our favourite fix is pairing an ANSI keyboard with Windows' United States-International layout: symbols stay where the table shows and ñ comes from AltGr + N. One thing to know first: on that layout the apostrophe, double quote, grave accent, tilde and caret are dead keys, so a lone quote means pressing it and then Space. It takes a couple of days to get used to, but it's maddening if it catches you mid-string.

2. Size: how much you use F keys and arrows

There's no universal answer; it depends on your editor and habits. In VS Code, for example, the default Windows shortcuts lean on the F row: F5 starts debugging, F9 toggles a breakpoint, F11 steps into a function, F12 goes to definition and F2 renames a symbol. On a 60% all of those live on the Fn layer, so each one becomes a two-key press.

How you work Format that fits Why
You debug daily with F5, F9, F11 TKL or 75% Physical F row, no combos
You live in the command palette and Ctrl shortcuts 60% or 65% What you use stays put and you gain desk space
You edit a lot by moving with arrows 65% Physical arrows without the F row
You move between laptop, office and home 60% The smallest footprint in a backpack

Our take: if most of your shortcuts are Ctrl, Shift and letters, a 60% falls short far less than it looks. And if there are two or three F keys you hit constantly, VS Code's keyboard shortcuts editor lets you move them to another combination. We go deeper in the 60% keyboard guide, including where the grave accent usually ends up, which matters because Ctrl + ` toggles the terminal in VS Code.

3. Switches: noise matters more than speed

Coding isn't a keystrokes-per-second race. What it does involve is calls, pair programming and open-plan offices. So for programming we'd rule out clicky switches unless you work alone, and choose between linear and tactile by taste: tactiles tell you when the key has registered, linears feel smoother and more neutral. The differences, with measured forces and travel, are in our linear vs tactile vs clicky switches guide.

A practical tip: if your keyboard is hot-swap, you don't have to get it right first time. Swap a few switches on the keys you use most and compare for a week.

4. Keycaps: built for the keys you hit most

Ctrl, Shift, the spacebar and the symbol keys take the most wear when you code. According to Wooting, ABS is softer and turns shiny with use, while PBT is harder, resists wear better and has a texture that collects less grease. If it's also doubleshot, the legend is a second layer of plastic and won't rub off. For a keyboard you'll use eight hours a day, PBT doubleshot is what we'd look for.

5. Connection: cable at the desk, wireless on the move

Plenty of developers switch between a laptop and a desktop, or between office and home. A keyboard with both cable and wireless saves you owning two. The cable is still the simplest choice for a fixed desk, with nothing to pair; Bluetooth is handy for tablets or laptops with no free ports, and a 2.4 GHz receiver is another wireless route when Bluetooth isn't available.

Summary: what to look for and what TESSEN has

Criterion What to look for when coding TESSEN keyboard
Layout ANSI if you write a lot of code 60% ANSI, 61 keys
Size Depends on how much you use F keys and arrows 60%: no physical F row or arrows
Switches Linear or tactile; avoid clicky in shared spaces Gateron KS-3 Milky Pro Yellow, linear and lubed
Swapping switches Hot-swap to try others without soldering Hot-swap, 3- and 5-pin MX switches
Keycaps PBT doubleshot PBT doubleshot, MX stem
Connection Cable plus a wireless option Coiled USB-C, 2.4 GHz and Bluetooth 5.0

We make 60% keyboards, so we won't pretend ours suits everyone: if you live in the debugger on F keys, a TKL will give you less friction. If your day is writing code, jumping between files with Ctrl shortcuts and carrying your keyboard from place to place, the format fits well. You can design it key by key in the 3D configurator, for instance colouring the symbol keys you use most, and save the design with its Design ID. Prices start at €119.99 including VAT. Shipping, returns and warranty are covered in the FAQ.

Sources

BlogChoosing a keyboard

Keep reading

All guidesAll news