
When I think about people starting out in DevOps, the picture that comes to mind is someone at a kitchen table on a Saturday morning, announcing to the household that the Docker project will be finished by lunch. By dinner it is still running. By Sunday it has turned into a different project altogether. If that sounds like you, you are in good company, and there is nothing wrong with your skills. The trouble lies in how we guess. This primer explains why side projects stretch, introduces a few plain words for talking about it, and gives you a small habit that makes your next plan more honest.
A short story about a Saturday
Picture a learner who wants to wrap a tiny web app inside a container and put it online for a portfolio. The plan: two hours. The first hour goes to installing tools and fixing a permissions problem. The second goes to a build that fails for a reason that takes a while to find. The third, unplanned, goes to understanding why the image is so large. The fourth is spent on the write-up, which was never in the plan at all. Four hours instead of two, and the learner feels slow.
Nothing unusual happened. The guess simply contained only the visible work. This is the most common story in learning, and it is why the first term in our glossary matters so much.
Six words worth knowing
Estimate
An estimate is your spoken or written prediction of how long something will take, made before you start. It is a guess with some thought behind it, not a promise.
Actual
The actual is what really happened: the total time from starting to finishing, including the detours. It is the only number in this whole subject that cannot be argued with.
Ratio
Divide the actual by the estimate. Four hours against two gives a ratio of 2. A ratio close to 1 means a good prediction. A ratio of 3 means the task ate three times your guess. It is a single number that carries across projects of different sizes.
Hidden work
Hidden work is everything that must happen but was not in your mental picture: installs, fixes, reading error messages, writing notes. Beginners meet more hidden work than experienced people simply because less of the process is familiar.
Correction factor
A correction factor is the typical ratio from your own past projects. If your last five tasks averaged 1.8, then 1.8 is your factor, and you can multiply your next guess by it before you announce a plan.
Scope creep
Scope creep is the quiet growth of a task while you work on it. A “simple container” becomes a container plus a pipeline plus a monitoring page. It is partly responsible for overruns, but it is also a sign of enthusiasm, so do not scold yourself for it.
Why this matters for a growing career
People who build an online presence, whether through a personal blog, a portfolio of projects or open contributions, are judged partly by whether they finish things. Finishing depends on realistic planning. A learner who promises a weekly post and delivers three in a row builds more trust than one who announces a grand series and goes quiet. Understanding your own ratio is a quiet form of professional branding: it helps you promise what you can deliver.
A simple habit: the guess card
Take an index card, or a note on your phone. Before you begin a project, write the date, a few words about the task, and your estimate. When you stop, write the actual hours and the ratio. In one corner, jot a few words about the thing that surprised you. That is the whole habit.
After ten cards you will notice something. The surprises repeat. Maybe your container projects run long because of setup, while your writing tasks run long because of editing. Knowing which is which allows you to pad the right things, not everything.
Linking it to real learning topics
The habit is especially useful for tool-heavy topics. Take Docker, a favourite of many beginners. A task like cleaning up and organising images sounds like a quick chore, yet guides such as this practical piece on managing Docker images in engineering teams reveal how many decisions lie inside it: naming, tagging, cleaning up old layers, deciding what to keep. Those decisions are the hidden work, and if you read about them before you guess, your estimate will already be a bit more honest.
Mistakes are another source of time. A post such as a list of frequent beginner errors with Docker shows the sorts of problems that can swallow an hour without teaching anything new. When you hit one, record it on your card. Over time your own list of recurring errors will be more useful than any generic list, because it describes your habits.
What to do when the ratio is large
A high ratio is not a failure. It is an invitation to look closer. Ask three questions. Was the task bigger than I realised? Was I missing a skill that I picked up along the way? Did I get distracted? The first leads you to estimate more carefully next time, the second reminds you that learning counts as progress, and the third helps you set up your space better.
If every project has a high ratio, apply your correction factor and carry on. A factor of two simply means you should say “four hours” when your instinct says two. Over time, as your skills grow, the factor will usually fall, and you will be able to see that improvement in your own cards, which can be an encouraging thing to look at.
Two small traps for beginners
The first trap is guessing in your head and writing nothing down. Memory is generous, and a month later you will swear that you guessed four hours all along. The card prevents that kind of gentle self-deception. The second trap is quitting the habit after one bad ratio. A single awkward Saturday proves very little; it is the pile of cards that teaches you. Keep going until you have at least five, then look at them together.
A kind word on comparing yourself with others
Online, it is easy to see only the finished results of other people’s projects and none of their overruns. Remember that every polished tutorial hides a pile of unplanned hours. Your cards are a truer record than the highlights you see elsewhere, and the only comparison that matters is between your guess and your own result.
Where else to see this habit at work
Groups focused on learning often make a point of reviewing what they have done. The website of Cotocus Foundation belongs to a nonprofit organisation interested in technology, innovation and education, and its site is organised around programs, research, a community space and a blog. It is a pleasant example of an organisation that talks about its work in the open, which is exactly the spirit of keeping your own cards and sharing a lesson or two with fellow learners.
Your first week, step by step
- Choose a small project you already want to do.
- Write your estimate on a card before touching the keyboard.
- Work as usual and note the start and stop times.
- Write the actual hours, the ratio and one surprise.
- Repeat with a second small task before the week ends.
That is all it takes. In a month you will own a handful of cards, a first correction factor and, I hope, a slightly kinder view of your own pace. The side project will still take longer than you think. The difference is that you will now know by how much.








