1 – Sublime Text, Git, iTerm, Markdown, and Podcasts

Semantic Versioning – read about how that works. Look up “~>” symbol.

When to commit (in the Git sense): for smaller changes than you’ve been doing. The idea is that you can look through and find the one specific thing you were working on and check the last time you updated it and what you changed. I had been doing it once per work session, but that’s not enough.

In sublime text, use command-T to search file names you want to open or read. You can also search folders using the **/**/** format, and you just go as specific as you need to to find what you’re looking for. This is faster than using the folders on the side.

For Git, there is a hard wrap of 72 characters for the first line, and then 80 characters for all other lines.

Markdown – read about it from daring fireball and GitHub.

Get iTerm and use it instead of Terminal because it’s better. He will install his shell files with a bunch of shortcuts and customizations.

A monkey patch: a temporary fix that says “do this instead of what Rails says to do.” It should be used rarely and only when necessary.

People encrypt using BCRYPT instead of SHA because BCRYPT slows down the encryption process (it limits the speed). Individual users don’t notice, but someone trying to hack in wouldn’t be able to test nearly as many.

Listen to these three podcasts:

Subscribe to these three newsletters:

Go to these Austin meetups