DEV Community

Marcos P
Marcos P

Posted on

How a Weekend Hobby Turned Into a Free Code Typing & Telemetry Lab

A few months ago, I had a simple weekend idea: I wanted a clean, distraction-free web page where I could practice typing actual programming syntax instead of random dictionary words.

One feature inspired another:

  • First, I wanted authentic mechanical switch sounds without lagging the typing loop, so I built a low-latency Web Audio API synthesizer for Cherry MX Blue, Brown, and Red profiles.
  • Then, I wanted to see why I kept slowing down on brackets, arrows, and indentation, so I added 10-finger workload telemetry and key bigram latency detection (flagging slow transitions like ->, {}, or []).
  • Next came a catalog of [X]+ real code snippets across 40+ programming languages, ergonomics guides, and an interactive keystroke replay so you can watch your run back at 1x or 2x speed to spot hesitation points.

Before I knew it, what was supposed to be a small weekend script turned into TypingCompiler (https://www.typingcompiler.com), a developer-focused typing practice and telemetry platform.


Under the Hood (Tech Stack)

To keep keystroke registration crisp and avoid network bottlenecks mid-test, I built the platform with:

  • Next.js, React & Tailwind CSS for a dark-mode-first, minimal UI.
  • Client-Side Telemetry Engine: All WPM, raw WPM, bigram intervals, and finger-zone distributions are calculated locally in real time so there is zero input lag.
  • Web Audio API: Procedural switch acoustics generated on the fly rather than loading heavy external audio files.
  • Supabase for backend persistence and snippet management.

100% Free & Zero Login Required

Because this was built out of genuine passion for developer tools, my rule from day one was simple:

  • No paywalls.
  • No ads.
  • Zero forced sign-ups (you can jump right in and start typing in 1 click).

I just deployed the dedicated speed test arena:
👉 https://www.typingcompiler.com/typing-speed-test

You can pick between standard English prose or real syntax tracks (TypeScript, Python, Rust, SQL, and more) and inspect your full post-test metrics—including your velocity curve, keystroke replay, and finger workload breakdown.


I'd Love Your Honest Feedback!

Since this is an independent hobby project, I’m constantly looking for ways to refine the experience.

If you have a couple of minutes to give it a spin:

  1. How does the typing feel and keystroke responsiveness hold up at your usual speed?
  2. Did you encounter any quirks with your keyboard layout (ANSI/ISO) or browser?
  3. What programming languages, syntax edge cases, or telemetry metrics would you like to see next?

Thank you for checking it out!

Top comments (0)