It’s been 60 days, to the day, since my last blog post. In the midst of my busy day, I made the mistake of pulling up my blog, only to see that my blog hasn’t been updated for exactly two months. As I’ve stated before, my work life has found a way to interfere with my personal productivity. Since that always seems to be the case, why don’t I talk about my day job for a moment.
Everyday, life takes my to Cisco Systems, where I work as an engineer with the cloud services team. The goals for our team include the following:
With all of this, a massive amount of new production sites are in the works. This means that without a considerable amount of automation effort, none of this will be possible in a reasonable amount of time. That’s where I come in.
I humbly accepted the role as automation subject matter expert within the Architecture and Engineering group. That means I spend a lot of time interfacing with engineers from every team, getting intimately familiar with the implementation details behind each feature, then developing the automation code necessary to orchestrate the deployment of it. It is indeed a large task, and the job has kept me busy writing code, and documentation.
This leaves a lot to be desired during my personal productivity time. Still, I continue to try and make progress with all of the things I plan to achieve over the course of this year. As I’ve written about in the past, there’s a difference between ambition, dedication, and opportunity . Therefore, I think it’s probably a good idea for me to not only blog about what I’m learning in my personal time, but to also give back by sharing original thoughts and ideas. I’m sure that I have a number of topics to discuss out in the open that may be of interest to the minority of readers passing through to read about how I’m doing with my numerous failed attempts at my 180-day coding challenge.
Try and keep up, people. I know I will.