By 12:15 AM, he was no longer fixing a bug. He was orchestrating. Ctrl + Shift + A to find any action. Alt + Insert to generate a constructor. Ctrl + Alt + L to reformat the entire file. His hands danced over the keyboard like a pianist playing a Chopin étude. The code didn’t just compile—it surrendered .
He held his breath. Two chords. The test ran in 0.4 seconds. Red bar. He fixed the assertion. Ctrl + U, Ctrl + R again. Green bar.
Leo smiled. He reached behind his desk, unplugged his mouse, and put it in a drawer. He never used it again.
At 12:22 AM, he pushed the fix. The CI pipeline turned green. He leaned back, spun his chair once, and looked at the cheat sheet taped to his monitor. jetbrains rider keyboard shortcuts cheat sheet
A sound escaped him—a low, reverent “whoa.”
Three months ago, a senior engineer named Mira had left a single printed page on his desk. It was titled: JetBrains Rider Keyboard Shortcuts Cheat Sheet . At the time, Leo had glanced at it, muttered “I’ll learn them later,” and used it as a coffee coaster. The coaster now had a perfect brown ring over Find Usages .
His confidence flickered on. He scanned the sheet further. By 12:15 AM, he was no longer fixing a bug
He tried it. A search bar exploded in the center of Rider. No mouse. No clicking through menus. Just his hands on the keys. He typed OrderService.cs . Enter. The file opened before his second heartbeat.
Then, he remembered the PDF.
He pulled the crumpled sheet from under a pile of sticky notes. The first shortcut hit him like a slap: Shift + Shift — Search Everywhere . Alt + Insert to generate a constructor
It was 11:47 PM on a Tuesday, and Leo’s build was broken again.
Mira had written a note at the bottom in pen: “Your mouse is a lie. Real speed is ten fingers and no cursor.”
Ctrl + F12 — File Structure . A popup showed him every method, property, and field in the current file. He navigated to CalculateTotal() by typing its name. His mouse sat untouched, gathering dust.
But the real moment of transformation came when he hit a failing unit test. The old Leo would have clicked the test name, scrolled to the failure, and manually run it. The new Leo looked at the cheat sheet. There it was, in bold: Ctrl + U, Ctrl + R — Run Current Test .
Ctrl + T — Go to Implementation . He was on an interface, and with two keys, he jumped straight to the concrete class where the real bug lived. No more middle-click hunting.