Beach

Working from the Beach, thinking how to empower my team better

This year my whole extended family decided to extend our annual Hop’s family Beach Week to two weeks! While this was great, the two weeks in August could not have came at a worse time work-wise as there was a lot of activity going on and new work needed attention. Thus I decided to “work from home” the first three days of the our time at the beach. Of course, I would have loved to take the full two weeks, I have PTO days that was not the problem. [Read More]

Jenkins is a disease

The block-box of plugins robs teams of knowledge

Jenkins is by far the most widely used tool/platform used in DevOps. It is the automation workhorse for many an organization. Yet there are an issues with Jenkins that new wave of CI/CD tools address. This new code first CICD platforms like Gitlab CI, CircleCI, TravisCI, Etc. are well positioned to take on Jenkins workloads. But I am finding that many “DevOps” engineers really only know how work with Jenkins and its massive plugin eco-system. [Read More]

Why

what and how are good but why is the reason

Why we do DevOps Why we do DevOps is the most important question a DevOps teams needs to answer and understand. Without a solid reason why we are moving towards a devops way of working, the team really is just an automation team. DevOps is much more than just automation, and teams can and do fall into the trap of just automating processes and not focusing on the why the automation is needed. [Read More]

Always chasing a new tool

Quick feedback is a must

Does this sounds familiar, there are so many tools, and so much time lost trying to understand them. It seems like we are always chasing a new tool that might fix something in our process. Yet, this tool does a lot more than we need and we could get it done with a tool we already have. Moreover, by the time you get said new tool in house and running, it has been months and now you question do we really need to tool as process has changed. [Read More]