I recently started mentoring a young junior developer who wanted to learn about DevOps and Cloud Infrastructure Engineering.I heard the saying "teach once, learn twice" where in teaching something, you learn the subject better yourself once from my martial arts teaching long ago, and I agree.
The mentoring experience gave me an opportunity to dive into and examine what DevOps is, how it's supposed to be used and more importantly in my opinion, how and why it fails out in the real world.
In Part 1, we looked at the apps and other tools that I come across and use not only in my day to day work as a contractor, but also in my personal projects as well.
I wanted to list and give a brief overview and explanation of why I use the things I do, for the things I do ;)
In this post I'm going to look at Project Management tools and well as the applications and tools I use for CI/CD and 'DevOps' work.
In your professional life, you're going to come across and use a wide range of applications and tools to get the job done. I'm always amazed when looking over someone's shoulder (with their permission of course haha) and seeing how they do their "thing", even if we both do the same job, people will have their favourite apps and ways of doing things (some of it is insightful, others - annoying haha).
I wanted to list and give a brief overview and explanation of why I use the things I do, for the things I do ;)
In this post I'm going to look at the Operating System, text editors, Terminals and finally Desktop Management tools.
I only heard of DevOps maybe just over a year ago.
My career has always been about knowing how the whole system hung together as a whole. So I would know a little bit about everything. Hardware, software, networks, operating systems etc.
Getting to know each area was essentially also getting to know the people who operate those areas. You would get to know developers, and how they thought. Some thinking you agreed with. Some you'd already seen in other useless or lazy workers so it's no different for them.
With all this crazy technology around working as a devops engineer it's easy to get caught up designing and building something really complex that does a lot of stuff.
Sometimes it's the demands of the job that means you created something that did one thing. Added something else to it. And before you knew it, the "thing" has become a complicated behemoth that's now critical to the operation of the company (true story, I've seen "hacks" become 'the infrastructure').