Ten 10‑day DevOps projects
A developer shared a list of ten hands‑on DevOps projects that teams can build in about ten days using large language models, including a mini Terraform runner, a CI/CD engine and a container orchestrator intended for practical cross‑training. The post frames fast, project‑based work as a way to upskill staff without hiring externally. (x.com)
DevOps is the practice of turning software delivery into a repeatable system, and one developer’s July 2026 post turned that idea into 10 short build projects teams can use for training. (x.com) Pulkit Mittal’s post listed 10 projects that he said teams could build in about 10 days with large language models, including a mini Terraform runner, a continuous integration and continuous delivery engine, and a container orchestrator. The format was hands-on: build a small working version of a real tool instead of reading docs or watching courses. (x.com) Terraform is infrastructure-as-code software from HashiCorp: engineers write the desired cloud setup in files, then Terraform creates or changes servers, networks, and databases to match. A “runner” is the execution layer that takes that code, plans the changes, and applies them in a controlled environment. (developer.hashicorp.com) Continuous integration and continuous delivery, usually shortened to CI/CD, is the automated assembly line for software: code is tested, packaged, and pushed toward production through scripted steps. Container orchestration is the scheduler that decides where packaged apps run, restarts them when they fail, and scales them across machines. (docs.gitlab.com) (aws.amazon.com) That framing lands at a moment when platform engineering has moved from a niche operations function toward an internal product model for software teams. DORA, the Google-backed DevOps research group, said its 2024 report drew on responses from more than 39,000 professionals and highlighted both artificial intelligence in software work and the rise of platform engineering. (dora.dev) (research.google) DORA defines platform engineering as building shared internal toolchains, self-service workflows, and “golden paths” that make delivery more repeatable. Microsoft’s platform engineering guidance uses similar language, describing self-service and better developer experience as ways to improve security, compliance, cost control, and time-to-business value. (dora.dev) (learn.microsoft.com) The appeal of 10-day projects is that they compress cross-training into something concrete. A developer who builds a toy pipeline or orchestrator has to touch permissions, deployment logic, failure handling, logs, and state management, which are the same moving parts that show up in production systems. (aws.amazon.com) (developer.hashicorp.com) Large language models change the pace more than the target. Microsoft’s GenAIOps guidance and Azure DevOps samples describe using models and templates to generate, test, and automate parts of deployment workflows, while still wrapping them in version control, approvals, and environment rules. (learn.microsoft.com 1) (learn.microsoft.com 2) The caution is that a mini tool is still a mini tool. Production Terraform pipelines need remote state, access controls, and review gates, and DORA still measures delivery performance with operational metrics such as deployment frequency, lead time for changes, change failure rate, and failed deployment recovery time. (developer.hashicorp.com) (dora.dev) Mittal’s list reads less like a shopping guide and more like a lab manual for teams trying to learn by building. In a field built on automation, the shortest path to understanding is often to wire up a small version yourself. (x.com)
