How I Set Up My Developer Mac Workflow: Dock Groups, Terminal, and Tools
A practical guide to setting up a developer workflow on macOS: organizing your Dock by project context, essential tools, and tips for switching between tasks.
A sustainable developer workflow on macOS is less about which theme you use and more about how fast you can switch contexts—frontend polish, backend APIs, infrastructure, and human communication—without losing track of where tools live. Here is a setup that works for many solo devs and small teams in 2026.
Core idea: Mirror your mental model on the Dock. Name groups after outcomes (ship UI, ship API, keep prod healthy, talk to humans), not job titles. Otterdock supports apps, files, folders, and links in those groups; data stays local; macOS 14+.
Group 1: Frontend
Put your editor (VS Code, Cursor, or WebStorm), browser profiles you use for local dev, design handoff folders, and any Storybook or preview scripts here. Add a link to your staging URL. If you touch mobile, drop Simulator or Android Studio shortcuts beside the web stack. The point is one click cluster when you are in "pixels and components" mode. For a step-by-step guide on setting up groups like this, see how to group apps on your macOS Dock.
Group 2: Backend
Include terminals, API clients, database GUIs (TablePlus or similar), and folders that contain service repos or docker-compose files. If you run queues or workers locally, add the monitoring dashboards you open daily as bookmark files inside the group so you are not hunting browser tabs.
Group 3: DevOps
Terraform folders, kubectl cheat-sheet notes, VPN or tunnel utilities, and infrastructure Git remotes belong here—not mixed with app code. Some engineers also stash runbooks as Markdown files in this group so incident response starts from one place.
Group 4: Communication
Mail, Slack, Discord, Zoom, and your calendar live together so you can batch human time. Keeping them separate from coding groups reduces the temptation to context-switch every time a notification bounces. You can still leave one chat icon outside the group if you need always-on visibility.
Essential tools (beyond the Dock)
Pair Otterdock with a modern terminal (iTerm2), a Git client you trust (Tower, SourceTree, or plain CLI), Proxyman or equivalent for HTTP inspection, and Xcode when you touch Apple platforms. Install Rosetta on Apple Silicon if you still run x86 tools. Keep Homebrew or Mise for language runtimes so your shell profile stays reproducible.
Terminal setup tips
Use a shell framework lightly—Oh My Zsh or Starship are popular—or keep a minimal .zshrc with explicit PATH ordering. Version managers (nvm, fnm, asdf) should load once; duplicate eval lines slow every new tab. For SSH, prefer keys with agent forwarding only when you understand the risk; otherwise use per-host configs in ~/.ssh/config.
Why Otterdock fits this workflow
Otterdock enhances the Dock rather than replacing it: workflow groups with skins, click or hover popups, two groups on the free tier, and Pro at $6.99 direct (Mac App Store $2.99 planned). It stores configuration under ~/Library/Application Support/Otterdock/, which fits a privacy-minded dev setup since no data leaves your machine.
| Group | Example contents | Goal |
|---|---|---|
| Frontend | Editor, browsers, UI repos | Ship interface changes |
| Backend | APIs, DB tools, services | Ship logic and data paths |
| DevOps | IaC, tunnels, runbooks | Keep environments healthy |
| Communication | Chat, mail, calendar | Batch coordination |
Revisit the layout after each major project: rename groups that became vague, archive repos you no longer open, and delete duplicate shortcuts. A workflow is a living document—the Dock should reflect this week's reality, not every tool you installed last year. For more tools to complement your setup, check out the best macOS productivity apps for 2026.