6 Tools I always install

0xkoji - Jun 25 '19 - - Dev Community

1. Xcode

Basically, I use Xcode to write code for openFrameworks and sometimes write Swift. In addition, rarely use to build a lib from source code

https://developer.apple.com/xcode/

2. Homebrew

Homebrew is a free and open-source software package management system that simplifies the installation of software on Apple's macOS operating system and Linux.

I cannot live without this lol. I also use this on my Ubuntu machine.

https://brew.sh/

3. Visual Studio Code

I have tried sublime, atom and bracket. Eventually, keep using vscode.
I think the biggest reason was code command. Actually, we can add a command to open an app from iTerm/Terminal, but vscode doesn't need any settings which are easy. I like markdown preview function which doesn't need to install any plugins.

https://code.visualstudio.com/

4. iTerm + oh-my-zsh

This isn't necessary, but I prefer iTerm to Terminal.

https://www.iterm2.com/
https://github.com/robbyrussell/oh-my-zsh

5. Clipy

Clipboard extension app for macOS.

This is very useful to me since I have many snippets on this app. In addition, when I use my friends' machine to help them, I always think why you don't have Clipy lol.

https://clipy-app.com/
https://github.com/Clipy/Clipy

6. Boostnote

An open source markdown editor for Mac, Windows and Linux app.

I always use markdown instead of txt since my note is including some codes. This app doesn't have a sharing function via the internet so basically for local use.

Others

GitKraken
https://www.gitkraken.com/
Recently, started using Glo Boards.

VirtualBox
http://virtualbox.org/

AppCleaner
https://freemacsoft.net/appcleaner/

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .