Cmd+C, Cmd+V, Cmd+Z — the basics settle into procedural memory quickly. Beyond that, most shortcuts remain things we intend to learn eventually.

The resources are easy to find. Most applications expose shortcuts directly in their menus, publish reference pages, and allow custom key bindings. Yet a 2005 study by Lane, Napier, Peres, and Sandor found that even experienced users relied on keyboard shortcuts less than 10% of the time, and that time spent using a program had little relationship with keyboard shortcut proficiency. Exposure alone doesn't build skill.

What builds it is intentional repetition — and a willingness to be slower before you're faster. Fitts and Posner's three-stage model of skill acquisition describes the progression: cognitive (active recall, slower execution), associative (familiarity forming, still requires attention), autonomous (fires without thought). Remington, Yuen, and Pashler put a number on the crossover: after roughly 200 repetitions, keyboard shortcuts became consistently faster than menu navigation. A new shortcut might cost you a beat every time you reach for it on day one. By the end of the first week of consistent use, that friction is mostly gone.

For developers working in digital environments all day, the environment itself is part of the work. Every unnecessary trip through a menu is a small interruption. Repeated across a session, across a week, those costs are real — and avoidable.

What follows is a practical reference organized by layer: operating system, browser, VS Code, terminal, and Git. The goal is not completeness, but a high-value subset of shortcuts and workflows that address genuine friction in day-to-day development.

Operating System

Developers move constantly between editors, terminals, browsers, documentation, and communication tools. A handful of OS-level shortcuts reduces the overhead of that navigation significantly.

Spotlight (Cmd+Space) deserves particular attention. It launches applications, locates files, performs calculations, and searches system settings — all without leaving the keyboard or touching the Dock or Finder.

Window Management

macOS Sequoia introduced native tiling via drag-to-edge. For keyboard-driven window management with more control, Rectangle (free) and Magnet (paid) both provide configurable shortcuts for snapping windows to halves, thirds, corners, and specific displays.

A typical development layout — editor on one side, browser or DevTools on the other, terminal on a second display — can be arranged entirely from the keyboard. Once those positions are muscle memory, context switching between tools stops requiring any deliberate navigation.

Browser

Browsers function as documentation readers, debugging environments, and research platforms throughout a development session.

Cmd+Opt+J / Ctrl+Shift+J opens DevTools directly to the console — no clicking through panels. For frontend work specifically, that one earns its place in muscle memory fast.

Cmd+L / Ctrl+L focuses the address bar immediately. Combined with typing a URL or search term and pressing Enter, it removes the mouse from routine browser navigation entirely.

VS Code

Navigation & Interface

Cmd+P / Ctrl+P opens any file by name — type a few characters and it filters in real time. With Cmd+B to hide the sidebar and Cmd+J to toggle the terminal, the file explorer panel becomes largely optional.

Cmd+Shift+P / Ctrl+Shift+P opens the command palette. For any action without a memorized shortcut, it's the fastest path.

Cmd+K, Cmd+S opens the full keyboard shortcuts editor. It's worth exploring — and anything that conflicts with existing habits can be remapped there.

Editing

Multi-cursor editing is worth investing time in. Selecting all occurrences of a variable, renaming across multiple lines simultaneously, or applying the same edit to a column of values — these are the kinds of tasks that used to require find-and-replace or repeated manual edits.

Terminal & Shell

Before building terminal shortcuts, it's worth knowing which shell you're actually in:

echo $SHELL

A shell is the command interpreter between you and the operating system — handling command execution, history, aliases, functions, environment variables, and startup configuration. Most modern macOS installations default to zsh. Personal configuration for zsh lives in:

~/.zshrc

After editing that file, reload it without opening a new terminal window:

source ~/.zshrc

The shortcuts and aliases in this section assume zsh, though most apply equally to bash.

Command Line Navigation

Ctrl+R initiates a reverse search through command history. Start typing any fragment of a previous command and it surfaces matches interactively — useful for long commands you remember running but don't want to retype.

Useful Commands

Display command history

history
history | grep git

Useful when you remember running a command but not its exact syntax.

Print working directory

pwd

The fastest way to confirm where you are in a directory structure.

View large files

less server.log

Unlike cat, less allows scrolling through large files without flooding the terminal output.

Repeat previous command

!!

A common use case: rerunning a command with elevated privileges after it fails without them:

sudo !!

Shell Customization

Aliases turn repetitive commands into single words. A few practical examples to add to ~/.zshrc:

alias ll="ls -la"
alias gs="git status"
alias gp="git push"

Small improvements compound. A few well-chosen aliases, combined with history search and readline shortcuts, reduce a meaningful amount of low-level friction every time a terminal opens.

Git

Common Commands

git status
git add .
git commit -m "message"
git push
git pull

git status is the most frequently useful of these. When uncertain about the state of a repository — what's staged, what's modified, what branch you're on — it provides an immediate summary.

Aliases

Add these to ~/.gitconfig under [alias]:

[alias]
  st   = status -sb
  aa   = add .
  cm   = commit -m
  ps   = push
  pl   = pull
  lg   = log --oneline --graph --decorate
  undo = reset HEAD~1 --mixed

Or as shell aliases in ~/.zshrc:

alias gst='git status -sb'
alias gaa='git add .'
alias gcm='git commit -m'
alias gps='git push'
alias gpl='git pull'
alias gl='git log --oneline --graph --decorate'

gl is worth calling out specifically. The --oneline --graph --decorate flags render commit history and branch structure in a format that's actually readable — a significant improvement over the default git log output.

Recovery Commands

Most Git commands create history rather than destroy it. A few commands that help when things go wrong:

Inspect unstaged changes

git diff

Review modifications before staging or committing.

Restore a file to its last committed state

git restore filename.js

Save work temporarily without committing

git stash

Useful when switching tasks mid-work. git stash pop restores it.

Switch branches

git switch feature-branch

A more explicit alternative to git checkout for branch switching.

Deliberate Practice

Reading about shortcuts can be useful. Acquiring them requires repetition. Deliberate action.

To accompany this article, I built a small workshop repository designed around that idea. The project walks through common development tasks using the same layers covered here — OS navigation, browser workflows, terminal commands, Git operations, and VS Code shortcuts.

Participants can fork and clone the repository, navigate the filesystem, open the project in VS Code, and complete progressively larger tasks. Instructions are embedded in the project files, and automated tests provide feedback as each task is completed.

Developer Shortcuts Workshop

Start Small

Pick one shortcut — ideally one that addresses something you actually do repeatedly. Use it every time that action comes up, even when it's slower than what you'd normally reach for. That's stage one of the acquisition arc. It's temporary.

By the end of a week of consistent use, the shortcut is close to automatic. At that point, add another.

The environment stops being an obstacle when the tools in it no longer require conscious attention. That happens one shortcut at a time.

Source Notes

Lane, D. M., Napier, H. A., Peres, S. C., & Sandor, A. (2005). Hidden costs of graphical user interfaces: Failure to make the transition from menus and icon toolbars to keyboard shortcuts. International Journal of Human-Computer Interaction, 18(2), 133–144.

"Results showed that shortcut use was very low (less than 10% of the time) and that the number of hours participants had been using the program did not predict the frequency of shortcut use."

Fitts, P. M., & Posner, M. I. (1967). Human Performance. Brooks/Cole.

Original source for the three-stage model of skill acquisition: cognitive, associative, and autonomous. The model describes how a learner moves from effortful, conscious execution of a skill toward automatic execution requiring minimal attentional resources.

Remington, R. W., Yuen, H. W. H., & Pashler, H. (2016). With practice, keyboard shortcuts become faster than menu selection: A crossover interaction. Journal of Experimental Psychology: Applied, 22(1), 95–106. DOI: 10.1037/xap0000069

"It is widely believed that a graphical user interface (GUI) is superior to a command line interface (CLI) for novice users, but less efficient than the CLI after practice. However, there appears to be no detailed study of the crossover interaction that this implies... The predicted crossover was observed after approximately 200 responses. Experiment 2 showed that following training all but 1 subject in the CLI-trained group chose to continue using shortcuts. These results suggest that frequency of shortcut use is a function of ease of retrieval, which develops over the course of multiple repetitions of the command."

Full References

• Lane, D. M., Napier, H. A., Peres, S. C., & Sandor, A. (2005). Hidden costs of graphical user interfaces: Failure to make the transition from menus and icon toolbars to keyboard shortcuts. International Journal of Human-Computer Interaction, 18(2), 133–144.
• Fitts, P. M., & Posner, M. I. (1967). Human Performance. Brooks/Cole.
• Remington, R. W., Yuen, H. W. H., & Pashler, H. (2016). With practice, keyboard shortcuts become faster than menu selection: A crossover interaction. Journal of Experimental Psychology: Applied, 22(1), 95–106. DOI: 10.1037/xap0000069
• Fagarasanu, M., & Kumar, S. (2003). Carpal tunnel syndrome due to keyboarding and mouse tasks: A review. International Journal of Industrial Ergonomics, 31(2), 119–136.
• Jardina, J. R., Peres, S. C., Nguyen, V., Megasari, A., Griggs, K. R., Pinales, R., & Amos, A. N. (2009). Keyboard shortcut users: They are faster at more than just typing. Proceedings of the Human Factors and Ergonomics Society Annual Meeting, 53(15).