Stop Sending Windows to the Dock

Photo by 85mm.ca on Unsplash

There’s a kind of computer fatigue that doesn’t come from hard work. It comes from recovery.

You’re writing, debugging, reading documentation, moving between a browser and an editor, keeping one eye on Terminal and another on a half-finished thought. Then the screen starts to crowd itself. Finder is sitting where it shouldn’t be. Mail is peeking out from behind the editor. Messages has appeared again. The browser has three windows open, and each one seems to think it has priority.

So you do the familiar thing. You hit ⌘ + M.

The window drops into the Dock. The screen looks calmer. Then, ten minutes later, you need the thing you buried.

That’s the tax.

As a long-time Vim user, I’ve developed a reflexive distrust of that tax. Vim trains the hand to stay close to the keyboard and the mind to stay close to the work. Movement becomes local, repeatable, and reversible. You don’t go hunting through the interface when one deliberate keystroke can put you where you need to be.

You don’t have to use Vim to recognize the feeling. Anyone who’s lost a thought while rearranging windows knows the cost. The mouse is useful, and sometimes it’s the right tool. But when the only job is to return to something you were just using, reaching for the pointer can feel like a small failure in the system around you.

That’s how I arrived at a small macOS rule: stop minimizing by default.

Minimization looks harmless. It looks tidy. It promises to get a window out of the way without closing it. On macOS, though, minimizing often turns an active object into a Dock problem. The window is no longer in the normal keyboard path. It hasn’t been closed, and it hasn’t been cleanly hidden. It has been set aside in a place you may now have to visually inspect, navigate toward, or recover through a sequence that feels like an apology.

The screen may look cleaner, but the work has become harder to retrieve.

That was the part I had wrong. I was treating visible clutter as the enemy, when the real problem was losing the working set.

The working set is everything still alive in the current session: the browser window with documentation, the Terminal window running a command, the draft, the notes file, and the Finder window pointed at the directory you keep returning to. All of that can be temporarily out of sight, but it shouldn’t be lost.

A useful workspace isn’t necessarily empty. It’s legible. The windows that belong to the current task should remain reachable. The windows that are finished should be closed. The apps that are alive but irrelevant should be hidden. The setup should help you return to the work without making you rediscover where the work went.

That’s the better rule underneath the rule: don’t chase a clean screen. Preserve the working set.

Once you think that way, the usual macOS commands stop feeling like random shortcuts. They become different answers to different questions. If you need another application, switch. If you need another window inside the same application, cycle. If the window is finished, close it. If the app is still useful but visually noisy, hide it. If the window is useful but badly placed, tile it. If you’ve lost the shape of the workspace, survey it. If the whole context has changed, move to another Space.

Minimization is weak because it answers too many of those questions badly. It’s a vague response to specific problems.

The first habit is to separate applications from windows.

On macOS, ⌘ + Tab moves between applications: browser, editor, terminal, mail, notes, calendar. It’s the broad sweep across working contexts. Once you build around it, the question changes. You stop asking, “Where did that window go?” and start asking, “Which app am I in?”

Inside the app switcher, macOS gives you two useful controls that are easy to miss. Hold ⌘ + Tab, select an app, then press H to hide it or Q to quit it. Those gestures separate two decisions that messy desktops often blend together: whether an app should remain open, and whether it should remain visible.

Some apps should keep running but leave the room. Mail, Messages, Music, Calendar, Slack, or whatever else fills the background of the day can stay alive without staying in your face. Other apps should be closed because the work is done. Keyboard control improves when those choices stay separate.

Once you’re inside the right app, the problem usually gets smaller and more irritating. You don’t need a different application. You need a different window inside the same application.

This is where ⌘ + ` does the work people often expect minimization to do.

The shortcut cycles through windows of the current app. If you have three browser windows, several Finder windows, multiple Terminal windows, or a few documents in the same editor, ⌘ + ` moves through that active set instead of sending one of those windows into the Dock.

If a window is still part of the job, cycle to it. If it’s finished, close it with ⌘ + W. If the whole app should disappear for now, hide it with ⌘ + H. That’s where minimizing starts to look imprecise. It doesn’t close the window. It doesn’t hide the app. It doesn’t preserve the window cleanly inside the normal cycling path. It creates a middle state that feels neat until retrieval begins.

Before building the habit around ⌘ + `, check the keyboard shortcut in System Settings. Keyboard, Keyboard Shortcuts…, and Keyboard can affect how a shortcut feels in practice, and the goal is simple: you want a dependable way to move through windows in the current app without sending anything to the Dock.

The desktop becomes easier to reason about when you stop treating it as one surface. macOS gives you layers, and each layer answers a different question.

⌘ + Tab answers the application question.

⌘ + ` answers the window question.

Tab shortcuts such as Control + Tab, Control + Shift + Tab, ⌘ + Shift + [, and ⌘ + Shift + ] answer the tab question.

🌐/Fn + Control + ← / → / ↑ / ↓ answers the layout question.

Control + ← and Control + → answer the desktop question.

For years, keyboard-first Mac users reached for third-party tools if they wanted fast window placement. Rectangle, Magnet, and similar utilities became part of the power-user kit because macOS had switching and Spaces, but not enough keyboard-native layout control. That’s less true now. Apple documents built-in tiling shortcuts for moving and resizing the active window, including Fn + Control + F for Fill, Fn + Control + C for Center, Fn + Control + ← / → / ↑ / ↓ for moving the active window to a half of the desktop, and Fn + Control + R for returning the window to its previous size.

That gives the workflow a missing verb: place.

Some window problems aren’t visibility problems. They’re geometry problems. A browser floating over a draft is noise; the same browser tiled beside the draft is useful. Terminal hidden behind three windows becomes something to recover; Terminal beside documentation can stay part of the work.

The 🌐/Fn + Control shortcuts let you fix the shape of the workspace without hiding the window, closing it, or turning the app into its own full-screen Space. A draft can sit on one side with research on the other. A note can be centered for temporary capture. An editor can fill the desktop without leaving the Space you’re already using.

That layout layer closes a real gap in keyboard-first macOS work. A lot of friction comes from using the wrong layer for the job: browser chaos is often a tab problem, a draft covered by a browser is often a layout problem, communication noise is often a hiding problem, and a finished preview is usually a closing problem. Minimizing all of it only makes the screen look cleaner.

The harder part comes in the middle of a session, after the work branches. You search for one detail and open two more pages. You check a file path and leave Finder open. You answer one message, and now Messages sits at the edge of your vision. Nothing is broken, but the room around the task has become harder to read.

That’s when ⌘ + M feels tempting. It gives you a quick visual fix. But the better move is to name the actual problem. Hide Messages. Close Finder. Cycle through the browser windows. Tile the browser beside the draft. Move research into its own Space if it keeps colliding with the writing.

The shift is simple: stop asking, “How do I clear this?” Start asking, “What kind of problem is this?”

Visibility management is the first practical answer.

⌘ + H hides the current application. ⌘ + Option + H hides everything except the current application. Apple’s Mac window guide lists Command-H for hiding the active app and Command-M for minimizing a window, which is the split this workflow depends on.

⌘ + Option + H is one of the cleanest ways to recover focus on macOS. It doesn’t close your work. It doesn’t rearrange the desktop. It doesn’t ask you to drag windows into position. It simply removes every other app from view.

You’re writing in an editor. Behind it sits a browser, Finder, Mail, Messages, Terminal, and maybe a simulator or two. You don’t need to minimize them one by one, and you don’t need to close them. ⌘ + Option + H leaves the editor in front and quiets the rest.

The point of hiding is to keep unfinished work alive without letting it shout at you. Mail can keep receiving. Messages can keep waiting. Music can keep playing. None of them needs to be visible while you’re trying to finish a paragraph.

That command feels minor until it becomes muscle memory. Then it changes the way the machine feels. The screen stops being a place where every open thing negotiates for attention. It becomes a surface you can narrow on demand.

There are times, though, when focus is too narrow. You need a survey.

Mission Control handles that layer. Control + ↑ shows open windows, and Control + ↓ shows windows for the current application. Apple documents Control + ↑ as a keyboard shortcut for Mission Control, and its Mission Control guide describes Control + ↑ as a keyboard way to enter Mission Control.

Mission Control works best as a map, not as the steering wheel. If you use it constantly, the machine may be telling you something: there are too many windows, too many half-finished tasks, or too many desktops with no clear job. Mission Control can show the mess, but it can’t decide what belongs together.

That’s where Spaces can help, if you keep them boring.

Spaces let you split work into separate desktops and move between them with Control + ← and Control + →. Used well, they turn one crowded surface into a few predictable rooms.

My own setup became clearer while writing. If research, messages, terminal output, and the draft all lived on one desktop, I kept managing the room instead of writing the paragraph. A browser window would cover the draft. Messages would pull the eye. Terminal would sit there like another unfinished thought. The workspace wasn’t broken, but it kept asking to be managed.

So I stopped trying to make one desktop behave well. I gave the work separate rooms.

One Space holds communication: Mail, Messages, Calendar. One holds research: browser, notes, PDFs. One holds writing. One holds development: terminal, editor, simulator, documentation. The setup isn’t elegant. It’s predictable enough that my hands know where to go.

Spaces fail when they multiply without responsibility. Ten desktops with vague jobs are clutter spread sideways. A smaller set is usually better. Communication, research, writing, and development are enough for most of my work. That gives me separation without turning navigation into another chore.

One macOS setting can either support that habit or sabotage it: automatic Space rearranging. macOS can reorder Spaces based on recent use. Some people like that because the last-used desktop stays nearby. For keyboard-first work, I prefer stable locations. If writing is always one Space away and development is always two Spaces away, the route becomes physical. When macOS rearranges those desktops, the map gets slippery.

Full-screen apps introduce a related problem. macOS treats a full-screen window as its own Space. Sometimes that helps, especially for a video call, a presentation, or a writing session that truly needs isolation. But if every app goes full-screen, your workspace can fragment into a long strip of isolated desktops. The screen looks clean, but the navigation gets worse.

This is one of the recurring traps in window management: the thing that looks clean can still make recovery harder.

Full-screen mode can hide clutter. So can minimization. So can too many Spaces. So can a carefully arranged set of third-party tools. The question isn’t whether the screen looks clean. The question is whether the work remains easy to return to.

Native tiling gives the active window structure without turning it into its own Space. For keyboard-first work, a tiled, maximized, or centered window often behaves better than full-screen because it stays inside the desktop structure you already understand.

The Dock is the awkward corner of this whole system.

If you truly need to recover a minimized window with the keyboard, Control + F3 can move focus to the Dock. On some keyboards, that may require Fn + Control + F3. Apple lists Control-F3 or Fn-Control-F3 as the shortcut to move focus to the Dock.

This works, but it’s also a sign that something upstream went wrong.

A recovery path is a poor foundation for daily work. If you spend the day getting good at retrieving minimized windows from the Dock, you’ve optimized the cleanup after a bad habit. Better to create fewer Dock problems in the first place.

There are still reasonable uses for minimizing. A long-running progress window may not need a whole app hide. A download status window or background utility may be fine tucked away. The point isn’t to treat ⌘ + M as forbidden. The point is to stop using it as the default answer to visual clutter.

Third-party tools can still refine the setup, but they can’t fix a confused working model.

Raycast can make launching apps, running commands, searching files, and triggering small automations faster. Rectangle can still go beyond Apple’s built-in tiling with custom shortcuts, thirds, quarters, multi-display workflows, and more opinionated layouts. AltTab can make window switching feel more like Windows or a tiling workflow. These tools are useful, and I use tools like this because macOS defaults aren’t always enough.

But tools work best when they extend a habit that already makes sense. Native tiling gives macOS a better baseline, but it doesn’t decide what belongs together. If every window is minimized, hidden, half-forgotten, full-screened into its own Space, and spread across too many desktops, more tools only give the mess extra controls.

The practical setup is small. Turn off automatic Space rearranging if you want desktops to stay predictable. Enable the shortcut for moving focus to the next window. Learn the 🌐/Fn + Control tiling layer. Consider auto-hiding the Dock if it keeps pulling your eye. Avoid making every app full-screen unless you actually want every app to become its own desktop.

Then practice the grammar in motion: switch apps, cycle windows, move through tabs, place windows with 🌐/Fn + Control, close finished work, hide background noise, survey only when the map is lost, and keep Spaces stable enough that your hands learn the route.

The test is simple: go one week without ⌘ + M.

Treat it as a diagnostic. Every time you want to minimize something, ask what you actually mean. Is the window finished? Close it. Is the app distracting but still alive? Hide it. Is the wrong window in front? Cycle. Is the window useful but badly placed? Use 🌐/Fn + Control + Arrow to tile it. Is the whole context wrong? Move Spaces.

That’s a better test than memorizing shortcuts. It reveals the shape of your own work. Maybe you have too many browser windows because research has no room. Maybe Messages isn’t the problem; your communication tools are simply living too close to your writing. Maybe full-screen mode looks peaceful but keeps breaking your route through the day. Maybe the Dock isn’t a convenience. Maybe it’s where unresolved window decisions go to wait.

By the end of the week, minimization starts to reveal itself for what it often is: a vague answer to a more specific problem.

That’s why I distrust ⌘ + M. Minimization feels orderly, but for keyboard-first work it often creates friction disguised as neatness. A hidden app is easy to return to. A cycled window remains in the active path. A tiled window stays useful without taking over the desktop. A stable Space preserves context. A minimized window too often becomes something you have to go find.

The Vim habit, transferred carefully to macOS, isn’t a moral stance against the mouse. The mouse is fine when it’s the right tool. The problem is reaching for it because your window system keeps losing the thing you were just using.

Never minimize when you can hide, switch, cycle, tile, or close.

The keyboard isn’t only faster. Used well, it keeps the work from scattering.