💡 macOS setup (tested on Tahoe). For devs who switch machines often, juggle between personal and client work, or are tired of reconfiguring everything by hand. Concrete promise: about 1 hour to put it all in place the first time, then 10 minutes to replicate the setup on any new Mac. The principles (versioned dotfiles, naming convention, fuzzy navigation) adapt to Linux/WSL, but part of the comfort (native
~/Developericon,brew) stays macOS-only.
⚠️ This article was previously written in French and was translated into English by AI.
Six building blocks that fit together:
~/Developer: a tidy root folderchezmoi: version your dotfilesghq: organize your repos without thinkingdev function: navigate at the speed of thoughtWhen you do dev work for a while, three pains keep coming back:
~/Documents/projects/old/v2-final/, sound familiar?).zshrc, .gitconfig, .ssh/config) only live on the current machine, and you struggle to recreate them on a new Maccd .. and an ls, sometimes moreThe default approach, dumping everything into ~/Documents/projects/ . It always ends in chaos. Worse: on recent macOS, Documents is synced with iCloud, which creates conflicts on .git folders.
Here's the setup that got me out. Six simple blocks that fit together.
macOS has a little-known feature: if you create a folder named exactly Developer directly in your home, it automatically gets a hammer icon. No config, it's native.
mkdir ~/Developer
killall Finder # in case the icon doesn't appear right away