Picking up DevOps can feel like standing in a downpour with a teacup. Containers one week, pipelines the next, then cloud networking, then monitoring. After a few months it is hard to say what you have really learned and what you have merely met. A done list is the cure: a running record of skills and exercises you have actually completed. Here are eight items worth putting on yours, each with a quick way to prove it to yourself.
1. A pipeline you built from scratch and ran end to end
Reading about continuous integration is one thing. Writing a pipeline that builds a small project, runs its tests and produces an artifact is another. Once it runs green from a clean start, write it down: the date, the tool you used and where the configuration lives. If you broke it on purpose and fixed it, even better. That line is worth ten tutorial bookmarks.
2. A container you packaged and then explained aloud
Build an image for a small application, run it, then explain to a friend what each instruction in the build file does. The explaining is the real test. If you can describe why you chose a base image or why a layer is ordered the way it is, add the item. If you stumble, leave it off and come back next week.
3. A deployment you rolled back
Anyone can push something out. A skill worth recording is returning to the last good state calmly when a release misbehaves. Practise on a throwaway project: deploy, break it deliberately, then roll back and confirm the previous version is serving traffic. Log it with a short note about what signalled the problem.
4. A script that replaced something you did by hand
The first time you automate a repetitive chore, however small, something clicks. Maybe it is a backup, a clean-up of old files or a report. Note what the task was, how long it used to take in a rough sense, and where the script is stored. The lesson here is not the script itself but the habit of noticing repetition.
5. Infrastructure described as code and rebuilt from nothing
Write a short definition of a small environment, such as a server with a firewall rule, apply it, delete everything and apply it again. When the second run works, you have shown that the definition is complete. Record the tool, the date and any surprises. Many learners skip the rebuild step and miss the point.
6. Monitoring that told you something true
Set up basic checks on a demo service and trigger a failure. Did an alert reach you? Was it clear? Add the item when the alert arrives and the message makes sense to someone who did not build the service. Should the message need a long squint to decode, reword it and test once more before you log it.
7. A gap you found and filled
Every learner has holes in knowledge, and finding one is progress. Perhaps you realised you did not understand how a network address range is split, or how secrets should be stored. Record the gap, then record the day you filled it and how you checked. For an organised way to hunt for such gaps, this article on the topics students tend to overlook while learning DevOps makes a good checklist.
8. A credential or course you completed, with the skills it left you with
If you have finished a structured course or exam, add it, but do not stop at the title. Under it, list the concrete skills you can now demonstrate. A bare certificate name tells a reader little; a handful of finished tasks tells a lot. To think about how formal qualifications fit alongside practical proof, see this discussion on what DevOps qualifications are actually worth in a tech career.
How to keep the list itself healthy
A done list for learners works best when it follows a few habits:
- Write the entry the same day you finish.
- Include a date, the tool or concept and where the evidence is.
- Keep one line per item, with an optional note.
- Review the list monthly to see which areas are thin.
- Delete nothing; if something fades, add a refresher entry.
Using the list in the real world
Your list will pay off in several ways. When you prepare for an interview, you will have real stories ready, each tied to something you actually built. When you apply for a course or role, you can point to specifics instead of general enthusiasm. When you feel discouraged, a quick scroll upward shows the ground already covered.
Nor does the habit need to stay inside technology. Suppose you are planning a trip to a conference abroad and you read about MotoShare, whose pages are in Indonesian and talk about renting bikes and cars via local partners. When the travel question is settled, a single line goes on your done list, and you can get back to your studies.
A quick example of a month’s entries
To picture the result, imagine a learner’s page after four weeks. Week one: a pipeline for a small web project, green from a clean start. Week two: the same project packaged as a container and explained aloud to a study partner. Week three: a rollback rehearsed after a deliberately broken release. Week four: a backup script written to replace a manual copy job. Four short lines with dates and evidence locations. Nothing flashy, yet each line gives you something concrete to discuss when asked, and a skill you can repeat on demand.
Pitfalls for learners
A common trap is logging tutorials as achievements. Following instructions step by step proves you can follow instructions. The test is whether you could repeat the task without the tutorial. Another trap is adding too many tiny items so that real milestones disappear. Group small exercises under a heading, and keep headline entries for the bigger ones. A final trap is silence: if a month passes with no entries, that is information too. Take it as a nudge to do something concrete this week.
Your starting move
Open a blank page. Add the heading Done. Write the first entry for something you completed this month, using the pattern of date, what you did and where the evidence lives. Then pick one of the eight items above that you can finish this week, and go do it. Give it a season and the page will prove your progress far better than memory ever could.

