If you write code, you already know the feeling: you can sit for hours solving problems - and your hands quietly pay the bill.

At first it’s nothing. A little stiffness. A weird tightness in the forearm. A wrist that “reminds you” it exists.

Then one day it stops being background noise and becomes a topic.

That topic is often RSI.

This post is a practical guide to RSI for programmers and heavy keyboard users:

  • what RSI is (and what it isn’t)
  • common stages you may go through
  • how to prevent RSI in two complementary ways:
    • what you need to do (habits + workstation)
    • how ergonomic keyboards can help

Note: I’m not a doctor. This is practical ergonomics, not medical advice. If you have numbness, weakness, night pain, or symptoms that persist, talk to a medical professional.

What is RSI (Repetitive Strain Injury)?

RSI is an umbrella term for pain or dysfunction caused (or aggravated) by repetitive movement, sustained positions, and overuse-often combined with stress, poor recovery, and suboptimal ergonomics.

For keyboard users, RSI commonly shows up in:

  • wrists
  • forearms
  • elbows
  • shoulders/neck (yes, really)
  • fingers and thumbs

RSI is not a single disease. It often overlaps with specific diagnoses like tendinopathy, tenosynovitis, nerve compression issues, etc.

RSI vs carpal tunnel (quick clarification)

People often say “RSI” when they mean “carpal tunnel” (or the other way around). A useful simplification:

  • RSI: broad overuse/strain category, many possible tissues and patterns
  • Carpal tunnel syndrome: a specific nerve compression problem (median nerve at the wrist)

If your symptoms include numbness/tingling in specific fingers, especially at night, don’t treat it as “just fatigue”.

External references (high level, non-controversial):

RSI stages for programmers and keyboard-heavy work

RSI rarely appears as a single dramatic event. For most people it’s a slow progression.

Here’s a practical “stages” model I’ve found useful. It’s not a clinical scale-just a way to recognize patterns early.

Stage 0: warning signs (the “ignore it” phase)

  • stiffness after long sessions
  • mild discomfort that disappears overnight
  • “hot” forearms after a high-intensity coding day
  • you notice you’re typing harder when stressed

This is the best time to act-because small fixes often work.

Stage 1: intermittent pain (you start adjusting unconsciously)

  • discomfort appears during typing, goes away with rest
  • you start stretching randomly
  • you change hand position frequently trying to “find relief”
  • you start blaming your mouse, then your keyboard, then your chair

Stage 2: persistent symptoms (performance starts to drop)

  • pain or tightness lasts into the next day
  • reduced endurance (shorter “comfortable typing” window)
  • you avoid certain shortcuts or key combos
  • you feel it during other activities (phone use, gaming, carrying bags)

Stage 3: nerve-like symptoms / functional limitation (do not push through)

  • tingling or numbness
  • weakness, dropping things, loss of fine control
  • pain that wakes you up at night
  • symptoms persist even with rest

If you recognize yourself here: stop treating it as “a productivity problem”. Get help. The goal is recovery, not hero mode.

Prevention track #1: what you need to do (habits + workstation)

Ergonomics is not a product. It’s a system.

You can buy the best keyboard on earth and still destroy your hands if you:

  • type with lifted wrists
  • squeeze the mouse like it owes you money
  • never take breaks
  • sleep badly for weeks

Here are the highest ROI habits.

1) Reduce continuous time (micro-breaks beat long breaks)

The issue is not “typing today”. It’s typing for 2 hours without changing position.

Tip: Aim for 30–60 seconds every 20–30 minutes. Stand up. Shake hands out. Look far away. Reset.

2) Fix wrist position first (neutral beats fancy)

For many people, the biggest pain generator is wrist extension (bent upward) and deviation (bent sideways).

If you want a visual explanation, see:

3) Type lighter (reduce force, reduce impact)

A lot of “keyboard pain” is simply too much force, repeated thousands of times.

Try this experiment: press keys as if the keyboard is expensive and fragile. Most people immediately reduce pain triggers when they stop bottoming out aggressively.

4) Use proper touch typing (it’s not about speed)

Bad habits are not just ugly-they are costly.

If you type with too few fingers, reach diagonally, or hover wrists, your body compensates in weird ways.

Start here:

5) Balance keyboard + mouse load

Programmers often forget: it’s not “keyboard RSI” or “mouse RSI”. It’s a combined workload.

Practical ideas:

  • learn 3–5 shortcuts that reduce mouse movement (one per week)
  • keep the mouse close (don’t reach)
  • alternate hands if possible for simple tasks

Prevention track #2: how ergonomic keyboards can help

Now the fun part: hardware.

An ergonomic keyboard won’t magically cure RSI, but it can remove common mechanical stressors-especially if your current keyboard forces your wrists into unnatural angles.

If you want the full overview of ergonomic features, start here:

Below are the biggest “why it helps” concepts.

Split keyboards: reduce wrist deviation and shoulder tension

Split keyboards let you place each half where your hands naturally want to be. That usually means:

  • wrists straighter (less ulnar deviation)
  • shoulders more neutral
  • less chest/neck tension during long sessions

Read more:

Tenting: reduce forearm rotation strain (for some people)

A flat keyboard forces forearms to pronate (rotate palm-down). Mild tenting can feel more natural.

Not everyone needs it, but if your forearms feel “twisted” at the desk, tenting is worth trying.

Ortholinear / columnar: cleaner finger travel

When keys are aligned in a grid (ortholinear) or in columns (column-staggered), your fingers can move more vertically and less diagonally.

That can reduce awkward reaches and micro-tension over time.

Related reading:

Programmability: fewer reaches, more stability

This is underestimated.

With a programmable keyboard you can:

  • bring heavy-use keys closer (Backspace, Enter, navigation)
  • move modifiers to more comfortable positions
  • reduce awkward stretches (especially for pinkies)

If you’re curious about going smaller with layers (and doing it safely), this is my perspective:

Low-profile and wrist posture

Lower keyboards can reduce wrist extension because your hands don’t have to “climb” up to the keys as much.

That’s one reason many people find low-profile boards comfortable for long sessions-especially without wrist rests.

A simple action plan (start today)

If you want a clean starting point, here’s a minimal plan:

  1. Record yourself typing for 30 seconds (seriously).
  2. Fix the biggest issue you see (usually wrists or force).
  3. Add micro-breaks (set a timer for a week).
  4. If you still feel symptoms, consider upgrading the keyboard setup (split, tenting, layout).

If you’re looking for a beginner-friendly hardware step, I recommend starting with split + ortholinear as a “low learning-curve, high benefit” combination:

Conclusion

RSI is not a moral failure and it’s not “just getting older”. It’s a signal that your workload + ergonomics + recovery are out of balance.

The best time to fix it is early-when symptoms are mild and changes are small.

You don’t need to do everything at once. Start with one improvement, then iterate. That’s how most real ergonomic progress happens.

Thanks for reading!
Bartosz