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.
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.
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 . jetbrains rider keyboard shortcuts cheat sheet
He pulled the crumpled sheet from under a pile of sticky notes. The first shortcut hit him like a slap: Shift + Shift — Search Everywhere .
Not just any broken—the kind of broken where the red squiggles under his C# code looked like a crime scene. His mouse hand was cramping from clicking between Solution Explorer, the editor, and the test runner. Every time he reached for the trackpad to find a file, he lost his mental context. He was a developer trapped in a point-and-click nightmare. At 12:22 AM, he pushed the fix
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 .
Then, he remembered the PDF.
Leo smiled. He reached behind his desk, unplugged his mouse, and put it in a drawer. He never used it again.
It was 11:47 PM on a Tuesday, and Leo’s build was broken again. He held his breath
A sound escaped him—a low, reverent “whoa.”