It includes iTerm2, zsh, Node, Visual Studio Code and some git commands.
- Install iTerm2
Change edit mode to natural text
- iTerm Preferences → Profiles → select your profile → Keys tab → Load Preset… → Natural Text Editing (See this StackOverflow answer)
New session should start where previous left off
- iTerm Preferences → Profiles → select your profile → General tab → Working Directory section → Reuse previous session’s directory option
Quit on tab close
- iTerm Preferences → General, “Closing” → “Quit when all windows are closed”
Increase font size
- iTerm Preferences → Profiles → select your profile → Text tab → Font section → Change font → Update font in the popup
- Fan of 16pt Monaco (12, 14 is just too small)
Enable infinite history
- iTerm Preferences → Profiles → select your profile → Terminal tab → Unlimited scrollback
With oh-my-zsh manager. Sets you up with auto-completion.
snazzy colour theme
Using iterm-snazzy, which is a case of downloading the
.itermcolors file and choosing the theme from (iTerm Preferences → Profile > Colors > Color Presets…).
It’s simple, clean but gives you enough information to be productive.
(see Setup and configuration for how to get Node/npm up and running)
- Install using npm:
npm install --global pure-prompt
- Initialise by adding the following to your
autoload -U promptinit; promptinit prompt pure
Browsers and testing
As a developer it’s always good to have a few browsers and tools handy:
- Google Chrome: still a goto due to its solid and extensive dev tools. Usually I install the React or Vue dev tools.
- Postman for Mac: to manually test APIs
- Firefox: number 2 browser
- Brave: auto-blocks ads and tracking, sort of the “play” browser, its dev tools are a buggier/less ergonomic version of Chrome dev tools (this is because Brave uses Chromium under the hood)
- Safari - installed by default on Mac OSX, it’s a buggy browser, good to test using it since it surfaces weird SVG and cookies security policy quirks. Since it’s the default it’s also widely used by non-technical people.
- Enable the dev tools: Safari → Preferences → Advanced → Show develop menu in menu bar.
I use Visual Studio Code, it strikes the right balance between usable out of the box and customisable. The way I see it editors like vim or Atom need a bit of config before being productive, and others like Sublime or IDEs (WebStorm) don’t have the same plugin ecosystem.
Install VSCode command line tools
Open the dialog using CMD + P.
Shell Command: Install 'code' command in PATH
The VSCode command line tool usage examples:
code .: open
.directory in VSCode
code -r .: replace directory opened in VSCode with the current directory
code -a .: add current directory to VSCode, ie. initialises a workspace
- Atom keymap: I’m not a fan of the default keybindings, this uses Atom-style ones, get it from the Visual Studio Marketplace or
ext install atom-keybindingsfrom
CMD + Pmenu
- EditorConfig for VS Code: “EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs.” (see editorconfig.org), ie. helps you deal with tab size, trimming spaces etc. across code editors, get it here from the Visual Studio Marketplace or
ext install EditorConfigfrom
CMD + Pmenu
Nice to have extensions
ext install vscode-eslintfrom
CMD + Pmenu
- npm Intellisense: “autocomplete npm modules in import statements”, get it from the Visual Studio Marketplace or
ext install npm-intellisensefrom
CMD + Pmenu
- Snazzy theme: same colour theme (snazzy) as I’ve got setup for the terminal for VSCode, get it from the Visual Studio Marketplace or
ext install snazzy theme
- Import Cost: “Display import/require package size in the editor”, get it from the Visual Studio Marketplace, or
ext install import-cost
Bump up the number of “inline items” (Clipy → Preferences → Menu → Number of items place inline).
Set your screenshots to save to clipboard + enable the option to paste as plain text (Clipy → Preferences → Beta → Paste as PlainText + Save screenshots in history).
Update Xcode using
Install Homebrew for package managements (think apt or pkg for Mac):
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Install Node.js either from source, using the Mac installer or using Homebrew:
brew install node
n – Interactively Manage Your Node.js Versions using npm (now that we have Node installed):
Switch to latest Node version using
sudo n latest
Install jq (format and deal with JSON nicely in the terminal) and watch (run a command repeatedly) using Homebrew
brew install jq watch
Add a few git extensions:
- git-open: “Type
git opento open the GitHub page or website for a repository in your browser.” using
npm install --global git-open
- git-standup: “Recall what you did on the last working day.” using
git standup, there are multiple install options (see git-standup#install), I usually go with:
brew install git-standup
- git-lg: simpler/prettier
git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit"
Setup and configuration
Add the following minimal
.vimrc, which enables syntax highlighting, has basic tab/tabsize configuration and enables line numbers display:
syntax enable set tabstop=2 set shiftwidth=2 set expandtab set number
Set up SSH keys and add to VCS hosting, see this GitHub help article:
- Generate a new key:
ssh-keygen -t rsa -b 4096 -C "*[email protected]*"
- Copy your public key to clipboard so you can paste it wherever your hosted Version Control system asks you to:
pbcopy < ~/.ssh/id_rsa.pub
Put percentage on power level, right-click the battery indicator and select “Show Percentage”.
Misc and extras
(Optional) Docker, VirtualBox
Subscribe to Code with Hugo
Get all the posts of the week before anyone else in your inbox