I'm using system design to learn cloud engineering
I like to describe myself as a technical writer with knowledge of cloud infrastructure. But now, I don't know if I'm a technical writer with cloud experience or a cloud engineer with technical writing experience. Still figuring that out. Anyhooo... I want to become really good at cloud engineering. Not just knowing how to use the tools, but understanding why they are used and how they affect…
The writer identifies as a technical writer with cloud infrastructure knowledge but is unsure if they are a technical writer with cloud experience or a cloud engineer with technical writing expertise. They aim to become proficient in cloud engineering, focusing on understanding the reasons behind the use of tools and their impact on business goals and decisions. This has led them to adopt a system design approach to their learning.
Over the past three weeks, the writer has learned the fundamentals of Linux, Docker, CI/CD, Terraform, and AWS. They have experienced frustration in learning these concepts, as mastering them reveals the vast amount of unknown knowledge. This realization leads to panic and a desire to learn everything, ultimately causing headaches.
To overcome this, the writer has shifted to a system design approach. By understanding the business decisions that influence tool usage, they hope to learn more effectively. They plan to immerse themselves in real-world or simulated scenarios rather than remaining in tutorial hell, learning concepts in isolation. Additionally, the writer intends to gamify their learning process.
They have enjoyed the Linux game Bandit and are open to discovering similar games for other tools, such as Terraform, AWS, Docker, and Git, which are essential for cloud and DevOps.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
