
Lotte started learning DevOps on a rainy January evening in Utrecht, with a laptop, a free account on a code-hosting site and a very long reading list. By March she had read three books and watched dozens of videos. She had also not deployed a single thing. A colleague asked her what she had built so far, and she realised the honest answer was nothing. That conversation changed how she studied. This beginner primer follows the path she took: put a tiny, imperfect project online early, and learn the vocabulary by using it. A mini-glossary sits in the middle so you can follow along without prior knowledge.
Why beginners get stuck reading
DevOps has a huge surface area: version control, containers, cloud services, automation, monitoring. A newcomer who tries to understand all of it before touching any of it will wait forever, because each topic opens three more. Reading feels productive and safe. Building feels risky because it exposes what you do not know. Yet building is where the vocabulary stops being abstract. The word “pipeline” means very little until you have watched one run and fail.
The answer is not to read less, but to give your reading a destination. Pick a tiny project that touches the main ideas once, in the simplest form, and let each concept arrive when you need it.
Lotte’s first version: a one-page site that deploys itself
She chose the smallest project she could think of: a single web page with her name and a paragraph about what she was learning. The goal was not the page. It was the journey the page took from her laptop to a public address, automatically, every time she changed it. In a weekend she had a repository, a short automation file and a live page. It was plain, slightly ugly and entirely real.
Mini-glossary: the words she met along the way
- Repository: a folder whose history of changes is tracked, so you can see what changed, when and why, and return to an earlier state.
- Commit: a saved snapshot of your changes with a short message describing them.
- Build: the step that turns your source files into something ready to run or publish.
- Pipeline: a chain of automatic stages (for example compile, check, publish) that fires each time you send in a change.
- Deploy: putting a version of your work somewhere people can actually use it.
- Rollback: returning to the previous working version when a new one misbehaves.
- Iteration: one round of change, release and learning; many small ones beat one large one.
Step by step: what she actually did
- Created a repository and committed a single file with her page.
- Wrote a short automation file that told the hosting service to publish the page after each change.
- Pushed a change and watched it go live, which took about a minute and felt like magic.
- Broke it on purpose by introducing a typo in the automation file, read the error message, and fixed it.
- Practised a rollback by returning to an earlier commit and seeing the older page reappear.
- Added one improvement per week: a basic check that the page contained her name, then a second page, then a custom address.
Each improvement taught a new term in context. When she added the check, she learned what a test is. When she set up a custom address, she learned a little about how names map to servers. None of it was studied in advance; it arrived because the project needed it.
What the career guides said, and when it started to make sense
Lotte had been reading career material for months without it sticking. It only came alive once she had something to hang it on. Articles such as a walk through the stages from junior to senior engineer started to read differently once she could place her own tiny project at the very first stage and see what the next one demanded. Likewise a longer map of skills, projects and certifications for a growing engineer suddenly had a “projects” section she could relate to.
If you come from support or system administration
Many beginners already work in IT operations, and for them the first project often means automating something they do by hand. A sysadmin might script the creation of a server and keep that script in a repository. The principle is the same: small, real, repeatable. Readers making that move will recognise themselves in guidance for operations staff switching into DevOps roles, and the first project there is the same as Lotte’s: one thing, automated end to end, shared with someone.
Showing it to the world, early
After a month Lotte wanted to share what she was learning, partly to stay accountable. She opened a blog on a free blogging site where each writer can pick a subdomain of their own, published a very short first post describing her one-page project, and went back to expand it as she understood more. The post was rough. Nobody minded, and two readers sent helpful suggestions in the first week.
One more habit worth copying: she kept a short list titled “things I did not understand yet” at the bottom of her repository notes. Each time a term confused her, it went on the list, and every Sunday she picked one item and learned it properly. After a few months the list was mostly crossed out. It gave her a calm way to deal with the feeling of being behind, because the gaps were written down and scheduled rather than looming. Beginners often underestimate how much that small bit of structure helps.
Three common beginner worries
- “My project is too simple to show.” Simple is the point. A working page with an automatic publish step demonstrates the whole loop.
- “I might break something.” You will, in a private sandbox where nothing depends on you. That is exactly where breaking is cheap and useful.
- “I do not know enough yet.” No one does at the start. The project is how you find out what to learn next.
Where Lotte is now
Months later, her one-page site has grown into a small portfolio with a few projects, each with its own pipeline. She still re-reads parts of her early writing and smiles at the mistakes, but she keeps the originals online because they show her progress. Her advice to the next beginner is short: do not wait until you understand everything. Put up the smallest working version of something this weekend, learn the words as you meet them, and improve it a little each week.