This document describes how I set up my developer environment on a new MacBook or iMac. We will set up popular programming languages (for example Node (JavaScript), Python, and Ruby). You may not need all of them for your projects, although I recommend having them set up as they always come in handy.
The document assumes you are new to Mac, but can also be useful if you are reinstalling a system and need some reminder. The steps below were tested on macOS High Sierra (10.13), but should work for more recent versions as well.
Contributing: If you find any mistakes in the steps described below, or if any of the commands are outdated, do let me know! For any other suggestions, please understand if I don't include everything. This guide was originally written for some friends getting started with programming on a Mac, and as a personal reference for myself. I'm trying to keep it simple!
- macOS Dev Setup
First thing you need to do, on any OS actually, is update the system! For that: Apple Icon > About This Mac then Software Update....
If this is a new computer, there are a couple of tweaks I like to make to the System Preferences. Feel free to follow these, or to ignore them, depending on your personal preferences.
In Apple Icon > System Preferences:
- Trackpad > Tap to click
- Keyboard > Key Repeat > Fast (all the way to the right)
- Keyboard > Delay Until Repeat > Short (all the way to the right)
- Dock > Automatically hide and show the Dock
- Mission Control > Hot Corners... > Top Right > Desktop
- Displays > Night Shift... > Schedule > Sunset to Sunrise
I recommend checking that basic security settings are enabled. You will be happy to have done so if ever your Mac is lost or stolen.
In Apple Icon > System Preferences:
- Users & Groups: If you haven't already set a password for your user during the initial set up, you should do so now
- Security & Privacy > General: Require password immediately after sleep or screen saver begins (you can keep a grace period of a couple minutes if you prefer, but I like to know that my computer locks as soon as I close it)
- Security & Privacy > FileVault: Make sure FileVault disk encryption is enabled
- iCloud: If you haven't already done so during set up, enable Find My Mac
Since we're going to be spending a lot of time in the command-line, let's install a better terminal than the default one. Download and install iTerm2.
In Finder, drag and drop the iTerm Application file into the Applications folder.
You can now launch iTerm, through the Launchpad for instance.
Let's just quickly change some preferences. In iTerm2 > Preferences..., under the tab General, uncheck Confirm closing multiple sessions and Confirm "Quit iTerm2 (Cmd+Q)" command under the section Closing.
In the tab Profiles, create a new one with the "+" icon, and rename it to your first name for example. Then, select Other Actions... > Set as Default. Under the section General set Working Directory to be Reuse previous session's directory. Finally, under the section Window, change the size to something better, like Columns: 125 and Rows: 35.
When done, hit the red "X" in the upper left (saving is automatic in macOS preference panes). Close the window and open a new one to see the size change.
If you're using iterm on a Mac you can enable "Natural Text Editing" which allows you to navigate by words using 'option + left/right'.
- Go to iTerm Preferences → Profiles
- Select your profile, then the Keys tab
- Click Load Preset... or Key Mappings -> Presets...
- Choose Natural Text Editing
Since we spend so much time in the terminal, we should try to make it a more pleasant and colorful place. What follows might seem like a lot of work, but trust me, it'll make the development experience so much better.
First let's add some color. There are many great color schemes out there, but if you don't know where to start you can try Atom One Dark. Download the iTerm presets for the theme by running:
cd ~/Downloads
curl -o "Atom One Dark.itermcolors" https://raw.githubusercontent.com/nathanbuchar/atom-one-dark-terminal/master/scheme/iterm/One%20Dark.itermcolors
curl -o "Atom One Light.itermcolors" https://raw.githubusercontent.com/nathanbuchar/atom-one-dark-terminal/master/scheme/iterm/One%20Light.itermcolors
Then, in iTerm2 Preferences, under Profiles and Colors, go to Color Presets... > Import..., find and open the Atom One Dark.itermcolors file we just downloaded. Repeat these steps for Atom One Light.itermcolors. Now open Color Presets... again and select Atom One Dark to activate the dark theme (or choose the light them if that's your preference).
Not a lot of colors yet. We need to tweak a little bit our Unix user's profile for that. This is done (on macOS and Linux), in the ~/.bash_profile text file (~ stands for the user's home directory).
We'll come back to the details of that later, but for now, just download the files .bash_profile, .bash_prompt, .aliases attached to this document into your home directory (.bash_profile is the one that gets loaded, I've set it up to call the others):
cd ~
curl -O https://raw.githubusercontent.com/nicolashery/mac-dev-setup/master/.bash_profile
curl -O https://raw.githubusercontent.com/nicolashery/mac-dev-setup/master/.bash_prompt
curl -O https://raw.githubusercontent.com/nicolashery/mac-dev-setup/master/.aliases
With that, open a new terminal tab (Cmd+T) and see the change! Try the list commands: ls, ls -lh (aliased to ll), ls -lha (aliased to la).
Now we have a terminal we can work with!
(Thanks to Mathias Bynens for his awesome dotfiles.)
Package managers make it so much easier to install and update applications (for Operating Systems) or libraries (for programming languages). The most popular one for macOS is Homebrew.
An important dependency before Homebrew can work is the Command Line Developer Tools for Xcode. These include compilers that will allow you to build things from source. You can install them directly from the terminal with:
xcode-select --install
Once that is done, we can install Homebrew by copy-pasting the installation command from the Homebrew homepage inside the terminal:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Follow the steps on the screen. You will be prompted for your user password so Homebrew can set up the appropriate permissions.
Once installation is complete, you can run the following command to make sure everything works:
brew doctor
To install a package (or Formula in Homebrew vocabulary) simply type:
brew install <formula>
To see if any of your packages need to be updated:
brew outdated
To update a package:
brew upgrade <formula>
Homebrew keeps older versions of packages installed, in case you want to rollback. That rarely is necessary, so you can do some cleanup to get rid of those old versions:
brew cleanup
To see what you have installed (with their version numbers):
brew list --versions
To list all formula for updating text file:
brew list --formula -1
To list all casks for updating text file:
brew list --cask -1
To export all formula, and casks from text file as dotfiles:
brew bundle dump
Then apply, and commit your changes via Chezmoi.
To install all formula, and casks from text file using Chezmoi, check out Chezmoi section.
A nice extension to Homebrew is Homebrew Services. It will automatically launch things like databases when your computer starts, so you don't have to do it manually every time.
Homebrew Services will automatically install itself the first time you run it, so there is nothing special to do.
After installing a service (for example a database), it should automatically add itself to Homebrew Services. If not, you can add it manually with:
brew services <formula>
Start a service with:
brew services start <formula>
At anytime you can view which services are running with:
brew services list
Chezmoi manages your dotfiles across multiple diverse machines, securely. With chezmoi, you can install chezmoi and your dotfiles on a new, empty machine with a single command.
Install chezmoi with your package manager with a single command:
brew install chezmoi
Initialize chezmoi with your dotfiles repo. This will check out the repo and any submodules and optionally create a chezmoi config file for you.
chezmoi init https://github.com/raksit31667/dotfiles.git
If you are happy with the changes that chezmoi will make then run:
chezmoi apply -v
Add/update your dotfiles, then commit your changes. For example:
chezmoi edit ~/.zshrc // This will open `~/.local/share/chezmoi/dot_zshrc`
chezmoi -v apply
chezmoi cd
git add .
git commit -m "Initial commit"
Update dotfiles as a submodule on this project:
git submodule update --remote --merge
git add .
git commit -m "update dotfiles"
Oh My Zsh is a delightful, open source, community-driven framework for managing your Zsh configuration. It comes bundled with thousands of helpful functions, helpers, plugins, themes, and a few things that make you shout... "Oh My ZSH!"
To export Oh My Zsh, including plugins and theme as dotfiles, run this command:
chezmoi add -r --exact ~/.oh-my-zsh
Then apply, and commit your changes via Chezmoi.
See Chezmoi section for more details.
For Spaceship ZSH, we need to run an extra command to symlink spaceship.zsh-theme to your oh-my-zsh custom themes directory:
ln -s "$ZSH_CUSTOM/themes/spaceship-prompt/spaceship.zsh-theme" "$ZSH_CUSTOM/themes/spaceship.zsh-theme"
Set ZSH_THEME="spaceship" in your .zshrc.
Oh My Zsh is installed by running one of the following commands in your terminal. You can install this via the command-line.
sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"
Once installation is done, install Homebrew and its dependencies, then replace default .zshrc with the one included in this repository.
sudo mv path/to/your/.zshrc ~/.zshrc
Refresh the terminal session with command-line:
source ~/.zshrc
To uninstall Oh My Zsh:
sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/uninstall.sh)"
Oh My Zsh comes bundled with plugins, which allow you to take advantage of functionality of many sorts to your shell just by enabling them. They are each documented in the README file in their respective plugins/ folder.
Clone your plugin repository into $ZSH_CUSTOM/plugins (by default ~/.oh-my-zsh/custom/plugins):
git clone https://github.com/your-plugin-repo ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/your-plugin-name
Add the plugin to the list of plugins for Oh My Zsh to load (inside ~/.zshrc):
plugins=(your-plugin-name)
Refresh the terminal session with command-line:
source ~/.zshrc
My plugins:
In order to enable a theme, set ZSH_THEME to the name of the theme in your ~/.zshrc, before sourcing Oh My Zsh; for example: ZSH_THEME=your-theme-name If you do not want any theme enabled, just set ZSH_THEME to blank: ZSH_THEME=""
My themes:
direnv is an extension for your shell. It augments existing shells with a new feature that can load and unload environment variables depending on the current directory. To install, simply run:
brew install direnv
For direnv to work properly it needs to be hooked into the shell. Each shell has its own extension mechanism. Once the hook is configured, restart your shell for direnv to be activated. Add the following line at the end of the ~/.zshrc file:
eval "$(direnv hook zsh)"
macOS comes with a pre-installed version of Git, but we'll install our own through Homebrew to allow easy upgrades and not interfere with the system version. To do so, simply run:
brew install git
When done, to test that it installed fine you can run:
which git
The output should be /usr/local/bin/git.
Let's set up some basic configuration. Download the .gitconfig file to your home directory:
cd ~
curl -O https://raw.githubusercontent.com/nicolashery/mac-dev-setup/master/.gitconfig
It will add some color to the status, branch, and diff Git commands, as well as a couple aliases. Feel free to take a look at the contents of the file, and add to it to your liking.
Next, we'll define your Git user (should be the same name and email you use for GitHub and Heroku):
git config --global user.name "Your Name Here"
git config --global user.email "your_email@youremail.com"
They will get added to your .gitconfig file.
On a Mac, it is important to remember to add .DS_Store (a hidden macOS system file that's put in folders) to your project .gitignore files. You also set up a global .gitignore file, located for instance in your home directory (but you'll want to make sure any collaborators also do it):
cd ~
curl -O https://raw.githubusercontent.com/nicolashery/mac-dev-setup/master/.gitignore
git config --global core.excludesfile ~/.gitignore
With the terminal, the text editor is a developer's most important tool. Everyone has their preferences, but if you're just getting started and looking for something simple that works, Visual Studio Code is a pretty good option.
Go ahead and download it. Open the .dmg file, drag-and-drop in the Applications folder, you know the drill now. Launch the application.
Note: At this point I'm going to create a shortcut on the macOS Dock for both for Visual Studio Code and iTerm. To do so, right-click on the running application and select Options > Keep in Dock.
Just like the terminal, let's configure our editor a little. Go to Code > Preferences > Settings. In the very top-right of the interface you should see an icon with brackets that appeared { } (on hover, it should say "Open Settings (JSON)"). Click on it, and paste the following:
{
"editor.tabSize": 2,
"editor.rulers": [80],
"files.insertFinalNewline": true,
"files.trimTrailingWhitespace": true,
"workbench.editor.enablePreview": false
}Feel free to tweak these to your preference. When done, save the file and close it.
Pasting the above JSON snippet was handy to quickly customize things, but for further setting changes feel free to search in the "Settings" panel that opened first (shortcut Cmd+,). When you're happy with your setup, you can save the JSON to quickly restore it on a new machine.
If you remember only one keyboard shortcut in VS Code, it should be Cmd+Shift+P. This opens the Command Palette, from which you can run pretty much anything.
Let's open the command palette now, and search for Shell Command: Install 'code' command in PATH. Hit enter when it shows up. This will install the command-line tool code to quickly open VS Code from the terminal. When in a projects directory, you'll be able to run:
cd myproject/
code .
VS Code is very extensible. To customize it further, open the Extensions tab on the left.
Let's do that now to customize the color of our editor. Search for the Atom One Dark Theme extension, select it and click Install. Repeat this for the Atom One Light Theme.
Finally, activate the theme by going to Code > Preferences > Color Theme and selecting Atom One Dark (or Atom One Light if that is your preference).
To sync-up all settings, including extensions, themes, and key bindings, install Settings Sync then refer with this Gist https://gist.github.com/raksit31667/fd9d40a03773c43b663aabd834d62716.
Java™ is the world's leading programming language and platform. AdoptOpenJDK uses infrastructure, build and test scripts to produce prebuilt binaries from OpenJDK™ class libraries and a choice of either OpenJDK or the Eclipse OpenJ9 VM. All AdoptOpenJDK binaries and scripts are open source licensed and available for free. However, AdoptOpenJDK officially deprecated in favor of the temurin casks provided directly from the Homebrew project, and will receive no further updates after 2021-08-01 (Aug 01, 2021). Please adjust your usage accordingly (see AdoptOpenJDK Homebrew GitHub).
Install Java 17 Temurin via Homebrew by running:
brew tap homebrew/cask-versions
brew install --cask temurin17
When finished, open your .bash_profile in the home directory (you can use code ~/.bash_profile), and add the following line:
# Java configuration
export JAVA_17_HOME=$(/usr/libexec/java_home -v17)
alias java17='export JAVA_HOME=$JAVA_17_HOME'
# default to Java 17
java17Save the file and reload it with:
source ~/.bash_profile
Every aspect of IntelliJ IDEA has been designed to maximize developer productivity. Together, intelligent coding assistance and ergonomic design make development not only productive but also enjoyable.
Configure the macOS keymap by going to Preferences > Keymap and selecting IntelliJ IDEA Classic.
Keeping Terminal history and auto-suggestions by navigating to Preferences > Tools > Terminal and unchecking Shell integration.
List of my installed plugins:
.ignore (4.0.3)
Atom Material Icons (35.0)
CheckStyle-IDEA (5.60.0)
EJS (203.5981.152)
Gitmoji Plus: Commit Button (1.7.0)
Go Template (203.7148.40)
Handlebars/Mustache (203.5981.152)
HashiCorp Terraform / HCL language support (0.7.10)
Karma (203.7717.11)
Key Promoter X (2021.1.1)
Kubernetes (203.7148.15)
MapStruct Support (1.2.4)
Material Theme UI (5.6.0.1)
Nyan Progress Bar (1.14)
Presentation Assistant (1.0.9)
Python (203.7717.81)
Redis Manager (1.2.2)
Robot Plugin (1.7.1)
Scala (2020.3.23)
SonarLint (4.14.2.28348)
WakaTime (12.0.7)
To share IDE settings on JetBrain accounts, check out this guideline: https://www.jetbrains.com/help/idea/sharing-your-ide-settings.html#settings-repository
Although VS Code will be our main editor, it is a good idea to learn some very basic usage of Vim. It is a very popular text editor inside the terminal, and is usually pre-installed on any Unix system.
For example, when you run a Git commit, it will open Vim to allow you to type the commit message.
I suggest you read a tutorial on Vim. Grasping the concept of the two "modes" of the editor, Insert (by pressing i) and Normal (by pressing Esc to exit Insert mode), will be the part that feels most unnatural. Also, it is good to know that typing :x when in Normal mode will save and exit. After that, it's just remembering a few important keys.
Vim's default settings aren't great, and you could spend a lot of time tweaking your configuration (the .vimrc file). But if you only use Vim occasionally, you'll be happy to know that Tim Pope has put together some sensible defaults to quickly get started.
Using Vim's built-in package support, install these settings by running:
mkdir -p ~/.vim/pack/tpope/start
cd ~/.vim/pack/tpope/start
git clone https://tpope.io/vim/sensible.git
With that, Vim will look a lot better next time you open it!
macOS, like Linux, ships with Python already installed. But you don't want to mess with the system Python (some system tools rely on it, etc.), so we'll install our own version using pyenv. This will also allow us to manage multiple versions of Python (ex: 2.7 and 3) should we need to.
Install pyenv via Homebrew by running:
brew install pyenv
When finished, you should see instructions to add something to your profile. Open your .bash_profile in the home directory (you can use code ~/.bash_profile), and add the following line:
if command -v pyenv 1>/dev/null 2>&1; then eval "$(pyenv init -)"; fiSave the file and reload it with:
source ~/.bash_profile
Before installing a new Python version, the pyenv wiki recommends having a few dependencies available:
brew install openssl readline sqlite3 xz zlib
We can now list all available Python versions by running:
pyenv install --list
Look for the latest 3.x version (or 2.7.x), and install it (replace the .x.x with actual numbers):
pyenv install 3.x.x
List the Python versions you have locally with:
pyenv versions
The star (*) should indicate we are still using the system version, which is the default. I recommend leaving it as the default as some Node.js packages will use it in their installation process.
You can switch your current terminal to another Python version with:
pyenv shell 3.x.x
You should now see that version when running:
python --version
In a project directory, you can use:
pyenv local 3.x.x
This will save that project's Python version to a .python-version file. Next time you enter the project's directory from a terminal, pyenv will automatically load that version for you.
For more information, see the pyenv commands documentation.
pip was also installed by pyenv. It is the package manager for Python.
Here are a couple Pip commands to get you started. To install a Python package:
pip install <package>
To upgrade a package:
pip install --upgrade <package>
To see what's installed:
pip freeze
To uninstall a package:
pip uninstall <package>
virtualenv is a tool that creates an isolated Python environment for each of your projects.
For a particular project, instead of installing required packages globally, it is best to install them in an isolated folder, that will be managed by virtualenv. The advantage is that different projects might require different versions of packages, and it would be hard to manage that if you install packages globally.
Instead of installing and using virtualenv directly, we'll use the dedicated pyenv plugin pyenv-virtualenv which will make things a bit easier for us. Install it via Homebrew:
brew install pyenv-virtualenv
After installation, add the following line to your .bash_profile:
if which pyenv-virtualenv-init > /dev/null; then eval "$(pyenv virtualenv-init -)"; fiAnd reload it with:
source ~/.bash_profile
Now, let's say you have a project called myproject. You can set up a virtualenv for that project and the Python version it uses (replace 3.x.x with the version you want):
pyenv virtualenv 3.x.x myproject
See the list of virtualenvs you created with:
pyenv virtualenvs
To use your project's virtualenv, you need to activate it first (in every terminal where you are working on your project):
pyenv activate myproject
If you run pyenv virtualenvs again, you should see a star (*) next to the active virtualenv.
Now when you install something:
pip install <package>
It will get installed in that virtualenv's folder, and not conflict with other projects.
You can also set your project's .python-version to point to a virtualenv you created:
pyenv local myproject
Next time you enter that project's directory, pyenv will automatically load the virtualenv for you.
The Anaconda/Miniconda distributions of Python come with many useful tools for scientific computing.
You can install them using pyenv, for example (replace x.x.x with an actual version number):
pyenv install miniconda3-x.x.x
After loading an Anaconda or Miniconda Python distribution into your shell, you can create conda environments (which are similar to virtualenvs):
pyenv shell miniconda3-x.x.x
conda create --name mycondaproject
conda activate mycondaproject
Install packages, for example the Jupyter Notebook, using:
conda install jupyter
You should now be able to run the notebook:
jupyter notebook
Deactivate the environment, and return to the default Python version with:
conda deactivate
pyenv shell --unset
If you installed an Anaconda/Miniconda distribution, you may start seeing an error message when using certain git commands, similar to this one:
pyenv: gettext.sh: command not found
The `gettext.sh' command exists in these Python versions:
miniconda3-latest
If that is the case, you can use the following workaround:
brew install gettext
Then add this line to your .bash_profile:
# Workaround for: https://github.com/pyenv/pyenv/issues/688#issuecomment-428675578
export PATH="/usr/local/opt/gettext/bin:$PATH"The recommended way to install Node.js is to use nvm (Node Version Manager) which allows you to manage multiple versions of Node.js on the same machine.
Install nvm by copy-pasting the install script command into your terminal.
Once that is done, open a new terminal and verify that it was installed correctly by running:
command -v nvm
View the all available stable versions of Node with:
nvm ls-remote --lts
Install the latest stable version with:
nvm install node
It will also set the first version installed as your default version. You can install another specific version, for example Node 10, with:
nvm install 10
And switch between versions by using:
nvm use 10
nvm use default
See which versions you have install with:
nvm ls
Change the default version with:
nvm alias default 10
In a project's directory you can create a .nvmrc file containing the Node.js version the project uses, for example:
echo "10" > .nvmrc
Next time you enter the project's directory from a terminal, you can load the correct version of Node.js by running:
nvm use
Installing Node also installs the npm package manager.
To install a package:
npm install <package> # Install locally
npm install -g <package> # Install globally
To install a package and save it in your project's package.json file:
npm install --save <package>
To see what's installed:
npm list --depth 1 # Local packages
npm list -g --depth 1 # Global packages
To find outdated packages (locally or globally):
npm outdated [-g]
To upgrade all or a particular package:
npm update [<package>]
To uninstall a package:
npm uninstall --save <package>
To install a package:
yarn add <package> # Install locally
yarn global add <package> # Install globally
To install a package and save it in your dev's dependencies:
yarn add <package> --dev
To see what's installed:
yarn list # Local packages
yarn global list # Global packages
To find outdated packages (locally or globally):
yarn outdated
To upgrade all or a particular package:
yarn upgrade [<package>] --latest
To uninstall a package:
yarn remove <package>
Like Python, Ruby is already installed on Unix systems. But we don't want to mess around with that installation. More importantly, we want to be able to use the latest version of Ruby.
The recommended way to install Ruby is to use rbenv, which allows you to manage multiple versions of Ruby on the same machine. You can install rbenv with Homebrew:
brew install rbenv
After installation, add the following line to your .bash_profile:
eval "$(rbenv init -)"And reload it with:
source ~/.bash_profile
The following command will show you which versions of Ruby are available to install:
rbenv install --list
You can find the latest version in that list and install it with (replace .x.x with actual version numbers):
rbenv install 2.x.x
Run the following to see which versions you have installed:
rbenv versions
The start (*) will show you that we are currently using the default system version. You can switch your terminal to use the one you just installed:
rbenv shell 2.x.x
You can also set it as the default version if you want:
rbenv global 2.x.x
In a specific project's directory, you can ask rbenv to create a .ruby-version file. Next time you enter that project's directory from the terminal, it will automatically load the correct Ruby version:
rbenv local 2.x.x
Check anytime which version you are using with:
rbenv version
See rbenv's command reference for more information.
RubyGems, the Ruby package manager, was also installed:
which gem
The first thing you want to do after installing a new Ruby version is to install Bundler. This tool will allow you to set up separate environments for your different Ruby projects, so their required gem versions won't conflict with each other. Install Bundler with:
gem install bundler
In a new Ruby project directory, create a new Gemfile with:
bundle init
Add a dependency to the Gemfile, for example the Jekyll static site generator:
source "https://rubygems.org"
gem "jekyll"Then install the project's dependencies with:
bundle install
Make sure you check in both the Gemfile and Gemfile.lock into your Git repository.
Update a specific dependency with:
bundle update <gem>
For more information, see the Bundler documentation.
Heroku is a Platform-as-a-Service (PaaS) that makes it really easy to deploy your apps. There are other similar solutions out there, but Heroku is among the most popular. Not only does it make a developer's life easier, but I find that having Heroku deployment in mind when building an app forces you to follow modern app development best practices.
Assuming that you have an account (sign up if you don't), let's install the Heroku CLI:
brew tap heroku/brew
brew install heroku
Login to your Heroku account using:
heroku login
(This will prompt you to open a page in your web browser and log in to your Heroku account.)
Once logged-in, you're ready to deploy apps! Heroku has great Getting Started guides for different languages, so I'll let you refer to that. Heroku uses Git to push code for deployment, so make sure your app is under Git version control. A quick cheat sheet (if you've used Heroku before):
cd myapp/
heroku create myapp
git push heroku master
heroku ps
heroku logs -t
The Heroku Dev Center is full of great resources, so be sure to check it out!
This really depends on how you want to organize your files, but I like to put all my version-controlled projects in ~/Projects. Other documents I may have, or things not yet under version control, I like to put in ~/Dropbox (if you have Dropbox installed), or ~/Documents if you prefer to use iCloud Drive.
You can customize Chrome on your desktop by adding extensions from the Chrome Web Store.
- JSONView Validate and view JSON documents.
- 1Password Password Manager.
- Vimium The Hacker's Browser. Vimium provides keyboard shortcuts for navigation and control in the spirit of Vim.
- uBlock Origin uBlock Origin is not an "ad blocker", it's a wide-spectrum content blocker with CPU and memory efficiency as a primary feature.
- Requestly Intercept & Modify HTTP(s) Requests - Modify Headers, Mock APIs, Throttle APIs, Insert Scripts, Block APIs/JS/CSS, Redirect URLs etc.
Here is a quick list of some apps I use, and that you might find useful as well:
- Portainer: Universal Container Management System for Kubernetes, Docker/Swarm, and Nomad. (Free)
- 1Password: Securely store your login and passwords, and access them from all your devices. ($3/month)
- Bruno: Fast and Git-Friendly Opensource API client. (Free for Opensource Edition)
- DBeaver: Free multi-platform database tool for developers, database administrators, analysts and all people who need to work with databases. Supports all popular databases. (Free for community features)
- Clipy: A Clipboard extension app for macOS. (Free)
- Bluesnooze: Prevents your sleeping Mac from connecting to Bluetooth accessories. (Free)
- Excalidraw: Online diagramming web site. (Free)
- RunCat: Provides a key-frame animation to the menu bar. Animation changes the speed depending on the CPU usage of Mac. (Free)
- Menu World Time: Get times for cities around the world straight from the menu bar. (Free)