The Cloud Letters
A newsletter for aspiring DevOps engineers.
Read all Cloud Letters
-
DevOps in the private cloud: Mastering the skills for the on-premise landscape
Private cloud is growing. We can expect more DevOps roles in future asking for private cloud skills. ‼️ Do you know what these skills are?
-
The Rise, Reign, and Reinvention of CentOS: A Linux Legacy
CentOS—the much loved Linux distro of DevOps engineers and Sysadmins alike—is now EOS. I know, some of you are still running it in production. But eventually those have to be replaced. What options do we have now?
-
How to run Kubernetes on bare-metal with cloud-like agility
Kubernetes is synonymous with agility and scalability—but that agility can be surprisingly elusive when your clusters are grounded on bare-metal.
-
How to use open source software at work (It's different from your home lab)
Understanding and leveraging open-source software (OSS) isn't just an advantage—it's a fundamental requirement in DevOps. But how you use OSS in an enterprise context is not like how you use it at home.
-
Private cloud Part 2: Why you should not build your private cloud on-premises
Do not build your private cloud on-premises unless there's a good reason to do so. Build your a private cloud off-premises.
-
DevOps in the private cloud - Part 1: How enterprises are using private cloud in 2025
Many DevOps practices rely on the agile nature of the public cloud. Private cloud is different. So, can you really do DevOps in the private cloud?
-
6 reasons why you should learn coding as a DevOps engineer: Even if you don't get to write code at the job
In this edition of The Cloud Letters, we talk about why all aspiring DevOps engineers should learn and practice coding.
-
5 formatting pitfalls to avoid in your resume: Only for DevOps engineers
Five things that you should not do when formatting your resume for your next DevOps job.
-
5 ways to build tech skills for your first DevOps job
If you want to land your dream job in DevOps, your cannot do it without building the right tech skills. Here's how you can build skills while you are still looking for your first DevOps job.
-
How to start learning Kubernetes on your home lab for free
Goal - Drive awareness of the importance of home labs for learning Kubernetes So what? why does this matter to aspiring DevOps (some people who has no clue on how to start learning Kubernetes) Aspiring DevOps engineers can easily create kubernetes home labs with multipass so what they can start practicing Kubernetes without spending any money Multipass based home labs can help you easily start practicing Kubernetes
-
7 mistakes to avoid in your resume when switching careers to DevOps with 10+ years of experience
Are you planning to switch into a DevOps career with 10+ years of experience in a different field? Avoid these 7 mistakes to build a compelling resume.
-
How to become a self-taught DevOps engineer before you turn 30
If I were in my twenties and wanted to become a self-taught DevOps engineer, here's how I would do it.
-
Are cloud certifications worth it
Why YOU want cloud certifications even though some others don't.
-
How to self-study for cloud certifications when you are working 9-5
If you've been wanting to do a cloud certification for many months but haven't made any progress read this to get started.
-
Containerization is not microservices
What is containerization and what is microservices. Many people mistakenly think that containerization and microservices mean the same thing. That's bad. Such peole get easily sold to ideas about modernization with microservices. Containerization is not microservices. Really? Then what is what? Containerization and microservices, often used interchangeably, mean very different things. So, what is containerization and what is microservices. And what is the reason for this confusion.
-
All you need to know about DevOps vs Site Reliability Engineering
DevOps vs Site Reliability Engineering is a topic that often lead to confusion. Is DevOps same as Site Reliability Engineering? Or is a DevOps Engineer different from a Site Reliability Engineer. Let's get this clarified.
-
The role of containers in DevOps
Containers were not created for DevOps. The intention of containerization was to share computing resources by running multiple application in isolation. But, DevOps today is simply impossible without containers.
-
DevOps job titles: Engineer vs Senior Engineer vs Staff Engineer and more
For the DevOps team, job titles create structure. For the individual, the job title defines competency. So, job titles are not just fluff.
-
How to write the job title for a career advancement
If I want to switch jobs with a career advancement, is it OK to give myself the new title I desire.
-
How to write the perfect job title in your resume
The job title in your resume will never be the sole reason for you to be hired. But it can be a reason for you to be crossed-off.
-
How to write a strong personal profile in your resume
Writing the personal profile is usually the hardest part in creating a resume. So, here's how you can write a punchy personal profile in just three steps.
-
The DevOps lifecycle is not so linear as it seems
The DevOps lifecycle shows a linear flow of activities in software development. But in real life, the flow is not so linear. seems like that activities flow linearly in the software development process. But this is not how things work in the real world. represents the application of DevOps practices in the software development process 1. how many: the number of ideas - 1 2. The what: what the reader gets - About the DevOps 3. The who: reader’s name - DevOps engineer 4. The why: the reason your reader should care - Understand the DevOps lifecycle 5. Twist the knife: answer here The DevOps lifecycle it's not so smooth as you may think. It's not just one big cycle. The simplest representation of DevOps. The continuoous cycle of software development. The DevOps lifecycle is not what you think it is
-
I want to be a DevOps engineer but I hear that DevOps is not a role
Originally, the DevOps practices did not define a role named DevOps engineer. But, today's software teams have a role named DevOps engineer. How did that happen?