
Your first month around DevOps will throw a pile of unfamiliar vocabulary at you, and few people mention that one of the handiest tools in the field is hardly technical at all. It is called a done list. What follows explains it from the ground up, shows how a newcomer can track learning with it, and closes with a small glossary for class or the office. Go at your own pace; no background is assumed.
First, what is a done list?
It is a page where you write down things you have finished. That is all. You probably already have a list of things you still need to do, whether on paper, in a phone app or in your head. A done list is the other half. When you complete a task, you do not just cross it out and forget it; you record it, adding a date and one line on how you can tell it is really done.
For a beginner this has a special benefit. Learning technology feels like climbing a mountain with no summit in sight, because there is always another tool to try. A done list shows the ground you have already covered.
What a beginner might put on it
- Installed a Linux virtual machine and logged in over a terminal.
- Created a small repository and made a first commit.
- Wrote a short script that renames files, and ran it successfully.
- Built a simple container image and started it.
- Set up a basic automated build that runs when code changes.
- Described a pipeline aloud, in ordinary words, to a relative with no technical background.
Each line is small, and each is real. Together they form a record that you can look at on a discouraging day.
Why finishing needs a definition
A common beginner trap is calling something finished when it only half works. The fix is to write a rule for yourself. For example: “An exercise counts as finished when I have run it myself, understood each step and could repeat it without the tutorial open.” Keep that sentence at the top of your list. It makes your entries trustworthy, which matters because later you will rely on them to decide what to revise.
Connecting your list to a career path
After a few weeks of entries, hold them up against a roadmap. Wondering how these early steps fit into a working life? A walk through how engineers grow from entry level toward senior roles makes a gentle starting point, while a fuller career roadmap spanning abilities, projects and exams stretches the view further. Read a single section, then glance back at your done list: which of those skills have you actually practised? Where are the blanks? Those blanks become your next study targets.
Mini-glossary
Eight words you will keep running into, put in everyday terms.
- Backlog: a holding area for requested work that nobody has begun.
- Definition of done: the shared checklist a team uses to decide that something is truly complete.
- Evidence: anything you can show to prove a task is complete: a green test run, a live service, a captured result.
- Changelog: a dated account of what was altered in a product, usually aimed at its users.
- Pipeline: an automated chain of stages carrying new code from a laptop toward a live service.
- Handover: the point where a piece of work or its ownership moves to someone else.
- Retrospective: a team conversation held after a stretch of work to talk through what to keep and what to alter.
- Rollback: putting a system back the way it was once a fresh change has misbehaved.
Do not try to memorise all eight in one sitting. Add each one to your own list when you first use it in practice; that is the quickest way to make a word stick.
A weekly rhythm for beginners
You do not need to write every day. Many beginners do best with one short session on the weekend. Open the file, add whatever you finished since last time, then pick two entries and ask, “Could I do this again from scratch?” If yes, the topic is solid. If not, schedule a repeat. This is gentle revision without drama.
Aim for a line or two per entry. Whole paragraphs mean you have drifted into diary territory, which is a perfectly good pastime but a different one.
You will notice this idea outside tech
Once you start looking, finished-step records appear everywhere. Anyone preparing a holiday keeps tabs on bookings made and documents handled. Even MotoShare, a website written in Indonesian that deals in online motorbike and car rentals, describes how it works as a sequence of stages, and anyone using such a service would be completing those stages one by one. The idea is ordinary, and that is exactly why it is easy to adopt.
Why the glossary words matter for your list
It helps to see how the vocabulary connects. A backlog feeds your plans, while the done list is where plans end up once they are completed. The definition of done is what gives each of your entries weight, because it says what had to be true before you wrote the line. Evidence is the thing you attach to prove it. A changelog is the outward-facing cousin of your personal record, and a handover is the situation where your list pays off most, since someone else can read it and carry on. Learning these links early saves confusion when colleagues use the words casually in meetings.
Mistakes beginners make, and kind corrections
Writing too much. Short entries are easier to maintain. Cut them down.
Only recording successes. You can also log a failed attempt as a finished piece of learning, as long as you note what you discovered.
Comparing your list with someone else’s. Everyone starts from a different place. The only useful comparison is your list today against your list last month.
Dropping it after a gap. Missing a few weeks changes nothing important. Add a line and carry on.
Your first ten minutes
Create a document and give it a title with the current month. Write your finish rule at the top. Under it, add three things you have already accomplished in your learning, however small. Save the file somewhere you will find again, and set a reminder for next weekend. That is the entire setup. Over the following months, the page will grow into a plain-spoken account of your progress, and when someone asks what you can do, you will have more than a feeling to offer.