The source Comand This will be a relatively short post, since the source command is pretty easy to use and there are really no options, but it’s an important command to know and use in your daily sys admin or dev activities. The source command will execute commands line by line from a file in the current shell. If you give any arguments to source, they become the positional parameters within the file.

The history Comand The history command is one of those rare commands that could change the way you live on the bash terminal, as it is a bash command that will show you the last commands to be entered in the users session. There are two states for history contents: The history list (in memory) The history file (on disk) When you type the history command into your terminal, you are interacting with your history list in memory, which will show you the last commands executed in your running session.

The next step in Infrastructure automation Over the last year I’ve been writing a ton of terraform. The tool is incredibly versatile and has allowed me to tackle just about any automation scenario when it comes to AWS infrastructure. It’s easy to use and easy to integrate into scripts or other automation. It’s a must have as a DevOps skill these days. But what is Terraform? If you’ve been in the DevOps space for any length of time, you’ve definitely heard of this tool.

Squashing And Why You Should Do It Squashing commits in git is something I originally would only do if my companies repo server like bitbucket or git has squashing upon merge enabled. However, it’s something you can do with the cli and vim pretty easily, and it makes your PR’s look amazing when you have everything under one neat commit ready to be merged into master. It also hides all those mistakes you made in those 300 commits of your feature branch…

Consistency, Consistency, Consistency In my career, I’ve seen many processes or policies that I have liked, and many that I don’t like. As you move from company to company you start to realize what works and what might not. Whenever I make a move, I tend to take some of those habits with me to the next place because frankly it just makes sense. This post will touch on those habits, and the things I do in my professional career (assuming the company doesn’t already have a policy or process that overrides it) that I’ve decided to keep using because I thought they were effective.

Straight To The Point Docker is a pretty mysterious thing to a lot of people these days and to be honest, it went right over my head the first time I heard about it. The idea of a container seemed not so special to me until I started to use it and understand the power this simple tool had to offer. My deployments got faster, my configurations were easier to manage, and using it was easier than expected.