FROM ZERO TO HERO
BECOME CRACKED AT VIM
From arrow keys to advanced motions, plugins, and editor hacks. 15 minutes a day. Three sample lessons below.
// CONCEPT
Move with h, j, k, l
VIM moves the cursor with h, j, k, l (left, down, up, right) instead of arrow keys. Once the muscle memory clicks, your hands never leave the home row.
Use right index for h and j, middle for k, ring for l — standard touch-typing fingering.
9 MODULES · 60 LESSONS · $28 LIFETIME · NO SUBSCRIPTION
// WHY BOTHER
WHY VIM IS WORTH LEARNING
$ cat why-bother.md
# 01 THE EDITOR DISAPPEARS
You stop thinking 'select line, hold shift, hit end, delete.' You hit dd and the line is gone. The thought happens, the code changes.
# 02 IT WORKS WHERE YOU ALREADY WORK
VSCode, Cursor, JetBrains, Obsidian, every SSH box, your browser, your shell. Learn the motions once and you have them in every editor you'll ever touch.
# 03 YOUR HANDS STAY ON THE HOME ROW
No mouse. No arrow keys. No four-inch reach every twenty seconds. Your fingers do the work your brain wanted done.
# 04 IT COMPOUNDS FOR THIRTY YEARS
The cracked engineers you watch ship - the ones with seven panes open at 2am - aren't faster because they care more. They're not fighting their editor.
$
// CURRICULUM
FROM HJKL TO YOUR OWN PLUGIN.
From mode awareness to plugin hacks. Each module ends with a hands-on drill.
// FOUNDATIONS · DAYS 1-4
M01
GETTING ORIENTED
Get the mental model so VIM stops fighting you. Install it, find your way around a buffer, and exit on demand.
:q!4 LESSONS
M02
MOTION
Navigate code at the speed of thought. Word jumps, character hops, marks, and screen-level motion - all without leaving the home row.
hjkl8 LESSONS
M03
OPERATORS + TEXT OBJECTS
Edit big chunks of code in one keystroke. Replace a function argument, kill an if-block, rename a variable in 3 keys.
ciw"foo"4 LESSONS
// FLUENCY · DAYS 5-9
M04
SEARCH + REPLACE
Find and replace across a 10k-line file faster than your IDE can think. The regex you actually need, no PhD required.
:%s/foo/bar/g4 LESSONS
M05
REGISTERS + MACROS
Record an edit once, replay it 500 times. Refactor whole files without writing a script or touching the mouse.
qa ... q @a4 LESSONS
M06
WINDOWS, BUFFERS, TABS
Juggle twenty open files without the mouse. Splits, jumps, and a workflow that scales past toy examples.
<C-w>v4 LESSONS
// MASTERY · DAYS 10-15
M07
EDITING AT THE SPEED OF THOUGHT
Refactor functions in under 10 keystrokes, edit JSON like a surgeon, kill every TODO in one line. The combos that turn VIM into reflex.
gg=G8 LESSONS
M08
CONFIG + PLUGINS
Build a config you understand line by line, with the handful of plugins that earn their keep. Skip the 2000-line dotfile cargo cult.
<leader>8 LESSONS
M09
VIM EVERYWHERE
VIM bindings inside VS Code, Cursor, JetBrains, your terminal, and your browser. Same keystrokes, every editor.
set -o vi4 LESSONS
48 lessons across 9 modules. Full lesson list inside after purchase.
// PRICING
GO FROM ZERO TO ADVANCED VIM IN 15 DAYS.
Interactive, in-browser lessons that drill VIM into your fingers. What takes most devs weeks of trial and error, you get in days.
// INCLUDED
- › 9 modules, ~60 interactive lessons, written guides for each
- › Drills and cheat sheets you can keep open at work
- › Future modules included. No upsells, no subscription.
- › Works wherever you code: terminal, VS Code, JetBrains, browser.
Secure checkout via Lemon Squeezy. Instant access.
- >But I can learn this for free.
- Sure. And in 6 months you'll know 8 motions and still reach for the mouse. This course is the curated path - same skills, minus the trial-and-error.
- >AI writes my code now. Why does editor speed matter?
- AI doesn't write code in a vacuum - you accept, edit, reject, and navigate around what it suggests. Editor speed is now collaboration speed. There's a reason VIM bindings ship inside Cursor, Copilot, and every modern AI tool.
- >I already use VS Code / Cursor / JetBrains. I'm fast enough.
- VIM bindings work inside all of them. You're not switching editors - you're upgrading the input layer. The lessons work in every one.
- >I tried VIM before and quit.
- Most people try to switch inside their real editor while shipping production code. The productivity dip kills the habit before muscle memory forms. Drill in your browser for 15 minutes a day, then bring the reflex back to your day job.
- >Why should I even bother?
- You'll edit faster, stop breaking flow, and stop touching the mouse. After 15 days you'll forget what fighting your editor felt like. Cracked devs use VIM. That's not the reason - that's the side effect.