BOOKS FOR MANAGEMENT

After being a manager for a few years, I’ve done well enough to have a few of the engineers I’ve managed become managers themselves. While I am moving back to an individual contributor role, I have spent a lot of time geeking out about management and it seems I have accumulated a good bit of knowledge. This post is meant to document some of the books I found useful learning to manage.

REQUIRED READING FOR THE CORONA VIRUS

I haven’t posted much recently, but the corona virus seems like a big deal. It reminds me of The Plague by Albert Camus. I highly recommend it. I’m starting to read it again.

MICROSERVICES WITH QUALITY PRESENTATION

Presentation from Austin Microservices Meetup Group about building Microservices with Quality:

LINDYFEST 2014 INVITATIONAL JACK AND JILL

I was invited to take part in the Invitational Balboa Jack and Jill at Lindyfest this year. I was paired with the fabulous Teni Lopez-Cardenas. Here is the video:

ROCKY MOUNTAIN BALBOA BLOWOUT 2014 OPEN STRICTLY

At Rocky Mountain Balboa Blowout this year, I completed with the amazing Deb Eason in the Open Strictly. We managed to get 1st place. Here is the video:

GETTING JENKINS TO WORK WITH LDAP

I sent up a jenkins server at work to help automate my teams builds and perform some basic testing on every build. One of the requirements for using it is that it must be secured. At work, we have an ldap server, which I previously used to secure our gerrit setup. Setting up jenkins to work well with the ldap server was a little for complicated. As a quick google search for “jenkins ldap slow” demonstrates.

THE GIT STAGING AREA

Git encourages users to think about what they are committing and one of the ways that it does this is with the “staging area.” Staging changes allows you to mark what changes should be included in the next commit. If no changes are staged, by default git commit won’t do anything. git status The ‘git status’ command can be used to show the contents of the staging area. There are three areas where a file may show up in git status:

USING GIT ALIASES

Git aliases provide a way to create shortcuts for complex git commands. To create a git alias: Open your ~/.gitconfig file Find or Add the [alias] section of the file. Add the aliases you would like to use. Aliases are added in the following form: alias_name = git command to be run After adding an alias, it can be executed using the git command, ‘git alias_name’