🚀 Crafting My Developer Workflow: VSCode, Vim, and Zsh

Source: Dev.to

“Imagine waving your hands like a conductor, and all the instruments play exactly what you want. That’s the feeling I chase every day in my workflow.”

As a developer you know the grind: hours staring at code, switching between files, terminals, documentation, and the browser. After years of building PHP, Laravel, and WordPress projects, my workflow was chaotic. I’d open VSCode, jump between files, repeat the same terminal commands, hunt for extensions, and tweak settings for hours—often working harder on my tools than on the code itself.

I decided enough was enough. I needed a workflow that would feel like music, where everything follows my rhythm.

Step 1: VSCode — More Than an Editor

VSCode is already powerful. I didn’t reinvent the wheel; I simply fine‑tuned it.

• Shortcuts – navigation, file operations, splits, multiple cursors, rename/copy/paste/delete.
• Automation – reduce repetitive actions.
• Editor tweaks – line numbers, relative lines, minimap, mouse‑wheel zoom, word wrap, cursor style.

These small changes together create a flow state: you move fast, think less about the tools, and more about your code.

Pro tip: Start with the basics and gradually adopt more shortcuts as they become intuitive.

Minimal. Clean. Focused.

I stripped away the visual noise:

• Tabs hidden, activity bar minimized, clean tree view.
• Vim keybindings for mouse‑free navigation and editing.
• Integrated terminal, Zsh, and shell tools.

It feels overwhelming at first—shortcuts everywhere, muscle memory required—but after a few weeks it becomes second nature, turning you into a coding “beast” that flows through projects without hesitation.

Step 2: Zsh — My Terminal, My Orchestra

With Oh My Zsh, plugins, and careful configuration, the terminal becomes your stage.

• Selective plugins – only the ones you actually use.
• Aliases – IP checks, file navigation, clipboard encoding, ports, battery status.
• Custom functions – e.g.:

# mkcd: create a directory and cd into it
mkcd() {
  mkdir -p "$1" && cd "$1"
}

# markdown2pdf: convert a markdown file to PDF using pandoc
markdown2pdf() {
  pandoc "$1" -o "${1%.md}.pdf"
}

• Clean PATH & MANPATH – no clutter, no confusion.

The result: less typing, faster navigation, and reduced mental friction.

Step 3: Extensions That Actually Work

Extensions are powerful when used purposefully.

• Install only what you need; each extension must have a clear purpose.
• Vim emulation focuses on essential motions (a, A, b, f, l, h, i, k, gg).
• Over 90 keybindings cover navigation, edits, file operations, and multi‑file workflows.

You can learn these Vim motions in 15–20 minutes on online platforms—well worth the investment.

Step 4: Why This Workflow Matters

• Personal yet universal – built on well‑known tools; anyone can adapt it.
• Speed & comfort – reduces repetitive stress and makes coding enjoyable.
• Scalable – works for PHP, Laravel, WordPress, and other languages like JavaScript, Python, Ruby.

Once you master the rhythm, coding feels like music: you think, you move, you execute.

Step 5: My Advice to Fellow Devs

• Start with your editor. Choose plugins you actually use.
• Automate the boring stuff. Aliases, functions, macros—small wins add up.
• Simplify navigation. Learn basic motions and shortcuts.
• Iterate. Your workflow evolves with your projects; don’t aim for perfection immediately.
• Enjoy the ride. Controlling your environment is like conducting your own orchestra.

Key Takeaway

Workflow isn’t about complexity; it’s about clarity, rhythm, and personal satisfaction. Start small, automate where you can, and let your tools follow your lead—not the other way around.

Find the complete configuration on GitHub:
https://github.com/mahafuz/.config