internaught.io A blog of questionable meaning...

Reality Bytes

This “Day and Age” we live in is dominated by a digital world that none of us can escape… I like to think I thrive in it.

Working @Rackspace

I’ve been living in San Antonio for a month now and every saturday I come to Rise Bakery & Cafe for a coffee and a panini. I’m still learning my way around but I can see myself as a regular at this place without a doubt.

I moved here from southern California after I accepted a position at Rackspace as a Linux Operations Engineer in their Email and Apps organization. Rackspace Headquarters is a 1.2 million square foot shopping mall converted into an office. It holds The World’s Largest Word Search Puzzle, a coffee shop and around 3,500 employees all under one roof.

In my last post, I mentioned that I was in the interview process. After four interviews, a round-trip flight to Texas and a few tweets later, I got an offer I was happy to accept.

From start to finish, Twitter played a huge role in the process.

Andy Pape, Dale Bracey, Drew Cox, Alan Bush and Faisal Misle were in contact with me pretty regularly and these guys are just as cool in real life as they are on social media!

One thing about Rackspace that sets it apart from any other company I’ve worked at, apart from the sheer size, is the community. You’re surrounded by honest, like-minded, cool people that most likely share a lot of the same interests as you do. Everyone is very accessible. The CEO sits at a desk like anyone else’s, not some big office, hidden away from everyone. The CFO has a hula-girl cutout in front of his desk, so you can easily identify his love of Hawaii.

Next month I’ll be in class at work. Rackspace has this thing called Rackspace University where employees go to get spun up on the latest and greatest technologies and even earn their certifications. I’ll be attending the week-long RHCSA course and hopefully earn my certification at the end of the course. Next step after that would be RHCE, of course but, I’ll take things one step a time.

A book has been floating around my department entitled “DevOps Troubleshooting: Linux Server Best Practices”. I bought this book and have only sat down to read it for less than an hour, but I can already say that it’s packed with practical linux troubleshooting methodology and a lot of not-so-common sense. I’m looking forward to soaking it up.

Equality for All

Eventhough horrible things are going on all around us, the human race is making some solid gains as well. The Supreme Court of the U.S. has (finally) made same-sex marraige legal, marking a huge step forward for the LGBT community. Hopefully this means we’re getting closer to coming together to solve bigger issues (take your pick) that are threatening the U.S. and the rest of the world. History has been made.

PvP or Perl vs. Python

I practiced writing Perl just about as much as I could. Joining the CPAN Pull Request Challenge was a great way for me to start contributing to open source projects while learning Perl. My dedication waxed and waned and eventually my interest just faded out.

At my new job, everything is Python. Python this and Python that and so I must join or die. Python forces you to use correct indentation where Perl could give a damn about how much whitespace you do or don’t use. I’m not sure which standard library is bigger or more powerful. All I know is, Python is industry standard. Which means, I’ve gotta start learning it and using it to make my tools or contribute to any one of the various projects in the company. I’m not convinced that this is entirely a bad thing, I just know I’ll miss using Perl.

I do plan on staying in the CPAN-PRC and tinkering with Perl on the side.

Grep | Awk

Interesting little thing I learned last week:

Many people, including myself as of last week, tend to get some output, search out what we want to keep using grep, then cut that output down even further using awk '{print $1}'.

You don’t need grep before awk. You can just awk '/grep/ {print $1}', like so:

Show all process ID’s owned by root.

#!/bin/bash

# You could grep root | awk {print $1}
ps aux | grep root | awk '{print $1}'

# Or you could do away with the grep entirely
ps aux | awk '/root/ {print $1}'

There is probably a lot of other stuff you could do using awk too.

Outro

Reminding myself to:

  • Read more books
  • Slow down, take things one day at a time
  • Stay humble
  • Practice mindfullness
  • Eat more fruits and vegetables

See you Space Cowboy.