BriteCore is a suite of web software that runs an insurance company. We're a remote-first organization, where nearly every employee works remotely, and we've been that way since the beginning.

We use modern technology that is ever-evolving, because that's how technology works. In order for our employees, business partners, and clients to be able to keep up with our technology, we decided to put this Awesome List together. We hope you find it useful!

• Development Environment
  • Make bash consistent
  • Install base tools
    • Xcode
    • HomeBrew
    • Git
  • Setting up Python
• Design
• Web Development
• Infrastructure

Our company develops almost exclusively on mac laptops, so this is currently geared toward that. Over the last 15 years we've tried just about everything you can imagine, but we like dead-simple now. The less we have to maintain on a development environment, the more software we get to build.

Update your .bash_profile to source .bashrc:

if [ -r ~/.bashrc ]; then
   source ~/.bashrc
fi

Then make a new .bashrc file if you don't have one already:

touch ~/.bashrc

Now you can make any bash changes directly in ~/.bashrc from now on, and that's the only place you need to make changes.

These are the first lines I added to my ~/.bashrc file:

# Infinite Bash History
HISTSIZE=
HISTFILESIZE=

# Better Prompt
export PS1="\[\033[36m\]\u\[\033[m\]@\[\033[32m\]\h:\[\033[33;1m\]\w\[\033[m\] $ "

# Terminal Colors
export CLICOLOR=1
export LSCOLORS=ExFxBxDxCxegedabagacad

xcode-select --install

Install Homebrew

brew install git

• Create SSH keypair
• Add public ssh key to GitHub account

If you want to see what branch you have checked out in your bash prompt, then add this to the top of your ~/.bashrc file:

parse_git_branch() {
    git branch 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/ (\1)/'
}

And modify your export PS1 line to read:

export PS1="\[\033[36m\]\u\[\033[m\]@\[\033[32m\]\h:\[\033[33;1m\]\w\[\033[m\]\$(parse_git_branch)\[\033[00m\] $ "

This was a great guide that we used as we created our specific steps which are below The definitive guide to setup my Python workspace by Henrique Bastos

brew install pyenv
brew install pyenv-virtualenv
brew install pyenv-virtualenvwrapper

Then add this to your .bashrc file:

# directory that contains the virtualenvs of all projects
export WORKON_HOME=~/.virtualenvs
# directory that contains the projects
export PROJECT_HOME=~/projects

# enable pyenv
eval "$(pyenv init -)"

# enable pyenv virtualenvwrapper plugin
pyenv virtualenvwrapper_lazy

# Enable auto-activation of pyenv-virtualenv
if which pyenv-virtualenv-init > /dev/null; then eval "$(pyenv virtualenv-init -)"; fi