Learners in DevOps are enthusiastic starters. A new tool appears, a new tutorial goes viral, and a fresh repository is created before the last one has a proper README. This FAQ addresses the questions students and early-career engineers ask when they are told to inventory what they already have before beginning another project. The answers are practical and concrete, and they apply equally to self-study, bootcamps and workplace upskilling.
Why should I inventory my own learning setup at all?
Because your setup is bigger than you remember. Over a few months of study, most learners accumulate local virtual machines, container images, cloud-account resources, repositories, bookmarked guides and half-finished notes. An inventory shows what is still useful, what is already working, and what actually remains to be learned. It also protects your wallet: forgotten cloud resources can keep consuming credits, and an overlooked subscription keeps renewing in the background.
What exactly goes on the list?
Aim for five categories:
- Code: repositories on your computer and on hosting platforms, with a one-line description of each.
- Environments: virtual machines, containers, local clusters and cloud accounts, including free-tier resources.
- Automation: scripts, pipelines, configuration files and scheduled jobs you wrote or copied.
- Knowledge: notes, bookmarks, course material and certificates in progress.
- Subscriptions: paid courses, tool licences, labs and hosted services with their renewal dates.
How long does a first pass take?
Plan on two to three hours for a thorough first pass, and shorter for a modest setup. Do it in one sitting if you can, because the point is to see the whole picture at once. A rough list is acceptable; accuracy improves with each review.
I only have a laptop and a free cloud account. Is there anything to inventory?
Yes, and it is probably more than you think. Check your shell history and home directory for scripts you wrote. Look at your container tool’s list of images and volumes. Open your cloud console and read the billing or resource overview page. Search your email for sign-up messages from learning platforms and tool vendors. Even a small setup tends to contain several projects, some abandoned and some quite close to finished.
What do I do with half-finished projects?
Mark each one as one of three states: finish, extend or archive. A project close to completion deserves a small push, because a finished, documented project is worth more to a hiring manager than three abandoned ones. A project that works but is simple can be extended with a new feature, which turns old work into a new learning opportunity. A project that no longer interests you can be archived, plus a line or two recording the lesson it taught. Our practical tutorial on starter projects that make a beginner’s portfolio shows how to arrange finished work so that it reads clearly to others.
Can the inventory help with my portfolio?
Very much so. A portfolio is a curated selection of the things you have already built. Without an inventory you tend to present whatever you remember most recently. With one, you can choose the three pieces that show a range of skills, such as a pipeline, an infrastructure definition and a monitoring setup, and polish them. That is a more efficient use of study time than starting from scratch.
What if I find duplicate projects?
That is common. Learners follow the same tutorial twice with different tools, or rebuild a similar web application three times. Compare the duplicates, keep the best documented one and merge anything unique from the others. If two versions use different tools, you may be able to present them together as a comparison of approaches, which is a more thoughtful story than two identical demos.
How do I know what skill gap remains?
Create a simple grid. Down the left, list the skills you want to show, such as version control, continuous integration, containers, infrastructure as code, monitoring and cloud basics. Across the top, mark where your existing work demonstrates each one. Blank cells are your genuine gaps. Those gaps, not whatever is trending this month, should determine your next project. For ideas on how to fill a gap, our guide to hands-on DevOps exercises that beginners can follow step by step offers suitable starting points.
Should I buy a new course before I finish my current one?
Check your learning inventory first. Many learners own several unfinished courses covering the same topic. Compare the syllabi, note which parts you completed, and decide whether the gap you found is already covered by material you hold. If it is, finish that first. If it is not, you now have a written reason for the purchase and can describe exactly what you are looking for.
How do I keep the inventory from becoming a chore?
- Store it in the same repository as your notes, so it travels with your work.
- Use a plain table with a handful of columns, not an elaborate system.
- Update it when you finish or abandon something, not on a schedule you will forget.
- Review it monthly for five minutes, checking for cloud resources still running.
- Add the date to each entry so you can see how your work has progressed.
Does this apply in a workplace, not just self-study?
Yes. Engineers joining a team often receive a pile of repositories, dashboards and credentials and are expected to find their way. A personal inventory of what you were given, what you understand and what is unclear accelerates onboarding and makes your questions more precise. Many managers appreciate a new hire who arrives with a list rather than a vague sense of being lost.
Is there anything worth reading outside DevOps?
Yes. Communities that run intricate systems often publish day-by-day notes. RobotsOps, for example, blogs about how robotics gets operated, and its pairing of a front page with a DailyLogs section shows the value people place on written records of ongoing work. The subject differs from yours, but the habit of writing things down is one every learner can adopt.
What is the single most important takeaway?
Before you start something new, find out what you already have. A short list of your repositories, environments, automation, knowledge and subscriptions will save money, prevent duplicate effort and make your next project sharper. It is a small piece of professional discipline, and it is one that employers notice when learners describe their work clearly.
Quick reference
- List code, environments, automation, knowledge and subscriptions.
- Mark each project as finish, extend or archive.
- Build a skill grid to reveal true gaps.
- Choose the next project to fill a specific gap.
- Update the list whenever something changes.
Return to this FAQ whenever you feel the urge to start something new. If the answer to “What do I already have?” is written down, the next step usually becomes obvious.

