{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreichjfoa4jzmjzby6eraqgdyoh2buesc5zfnn4lzdwvvg3wekreeji",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mqcxejrfv6p2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreicaqzeoa5uwv3jw7hi4r7nzbjuu5oamxhacpvkhsw4k4j26crkle4"
    },
    "mimeType": "image/webp",
    "size": 90920
  },
  "path": "/iriandr/why-im-learning-devops-in-public-4e4d",
  "publishedAt": "2026-07-10T19:35:03.000Z",
  "site": "https://dev.to",
  "tags": [
    "beginners",
    "devops",
    "learning",
    "linux"
  ],
  "textContent": "I just installed WSL2, set up Ubuntu, and ran my first Docker container.\nNothing groundbreaking — but it's the start of something I want to document\nproperly, so here we are.\n\n##  Why DevOps\n\nI want to work as a DevOps engineer, ideally starting with an internship.\nRight now I'm at the very beginning: comfortable with a computer, but new to\nLinux, containers, and most of the tooling this field runs on.\n\n##  Why write about it\n\nTwo reasons. First, writing forces me to actually understand what I did,\nnot just copy-paste commands that happened to work. Second, English isn't\nmy first language, and technical writing is a good way to practice it\nwhile doing something useful.\n\n##  What to expect here\n\nI'll be posting as I go through each stage:\n\n  * Linux and the terminal\n  * Git and GitHub workflows\n  * Docker, from basics to docker-compose\n  * CI/CD with GitHub Actions\n  * Kubernetes basics\n  * Infrastructure as Code with Terraform\n\n\n\nSome posts will be short notes, others will be closer to tutorials, written\nthe way I wish someone had explained it to me.\n\nIf you're on a similar path, feel free to follow along.",
  "title": "Why I'm Learning DevOps in Public"
}