
A few years into a DevOps career, many engineers hit the same quiet question: how do I become visible without turning into a full-time content creator? The two most common answers are writing posts and building side projects. Each has loyal advocates, and each has a way of fizzling out. I have watched colleagues start both with great energy and abandon both by March. This comparison looks at the two routes side by side, and at the one habit that determines whether either survives: always knowing exactly what you will do first next time.
Route one: the regular blog post
Writing in public has obvious appeal. It is cheap, it can be done in short bursts, and it leaves a searchable record of what you know. A well-kept page of notes on cloud tooling or incident lessons shows hiring managers how you think, not only what you have used.
The weakness is the blank page. “Write a post about containers” names a subject and nothing more, a mood rather than a job. Many would-be writers collect a long list of topics and then stare at it for forty minutes on a Sunday, because choosing among a dozen options is hard and starting is harder. Half-finished drafts pile up, each unremarkable on its own, together a quiet reproach.
Route two: the side project
A side project shows what you can do. A small deployment tool, a dashboard for your home lab, a pipeline template other people can copy: each gives you something concrete to show and talk about. Interviewers ask about projects far more readily than about prose.
Its weakness is scope. Projects balloon, and a Saturday idea becomes a three-month commitment with no visible edge. When you return after a busy week you face a repository, a vague memory of where you were, and no obvious entry point. Many projects die not from difficulty but from the ten minutes of confusion at the start of each session.
Where they genuinely differ
- Time to first visible result: a short post can exist in an evening; a project usually takes a few weekends to show anything.
- Evidence value: projects demonstrate skill directly; posts demonstrate thinking and communication.
- Restart cost: posts restart from a draft; projects restart from a codebase, which is heavier.
- Audience: posts can be found through search; projects are found through a link someone chooses to follow.
Neither is better in the abstract. The honest comparison is about which one you will actually keep doing, and that depends heavily on how easily you can restart it.
The shared fix: leave one precise next action
Both routes are rescued by the same small practice. When you stop, write one sentence that says exactly what to do first next time, with a verb and an object. For a post: “Write the first two sentences of the intro explaining the problem I hit with image sizes, then stop.” For a project: “Open the Dockerfile and add the line that copies the config folder; run the build once.” The instruction is deliberately modest. Its job is not to move the whole effort forward but to get your hands moving within a minute of sitting down.
For readers who want ideas for the technical side, a practical write-up on keeping container images tidy and manageable across a team is the sort of subject that produces both a decent post and a decent mini-project. And if you want to explain a concept to others, an article like the one setting Docker against virtual machines for newcomers shows how a familiar topic can be reframed for beginners.
A story of two attempts
Consider an engineer who wants a stronger public profile. In January the plan is a post every Sunday. By the third week, Sunday arrives with no topic chosen and a vague sense of obligation. The engineer scrolls, reads other people’s posts, and ends the evening feeling worse. In February the plan switches to a side project, a small tool for rotating test data. It goes well for two weekends, then work gets busy. When the engineer returns, the repository is a stranger.
The turning point is unglamorous. The engineer starts ending each session with a line at the top of a notes file: “Next: add the failing test for the empty-input case.” And for writing: “Next: draft the heading list for the container post, five headings, nothing else.” Both efforts begin to move again, not because they got easier but because the first minute stopped being a decision.
A note on reading and inspiration
Visibility also feeds on input. Many engineers keep up with ideas by browsing brief articles, and a blog-style website made of short learning-oriented pieces in a news layout, such as this site with trending and main-news lists, can be a prompt for what to write or build. The danger is the familiar one: reading about other people’s output can replace your own. Cap it. Take one item, close the tab, and carry out whatever your notes say first.
A realistic first month
Picture the opening weeks in concrete terms. In week one, whichever route you pick, the only goal is to prove that restarting works: two sessions, each ending with a written line and each beginning from it. In week two, add one small public artefact, either a short post or a tagged release of the project, however rough. In week three, look back at the restart times. If you can sit down and begin within a couple of minutes, the habit is taking hold. In week four, decide whether to keep the route, swap it, or run the two in alternation. Notice that none of these weeks is measured by audience size. Visibility tends to follow consistency, and consistency follows cheap restarts.
Choosing between the two, practically
- If your restarts are short and scattered (commutes, gaps between meetings), favour posts. A paragraph fits in ten minutes.
- If you have longer, rarer blocks (a free Saturday morning), favour a project, but keep its scope tiny and its first step written down.
- If you are unsure, alternate: let a project’s lessons become a post, and let a post’s idea become a small project.
Mistakes that undermine both
- Writing aims (“build my brand”) rather than actions (“open the draft and write the opening line”).
- Keeping several next-step lines, which turns into a menu and invites delay.
- Letting the line go stale after a change in plan.
- Judging the effort by output volume instead of consistency of restarts.
The practical conclusion
Writing builds your voice and projects build your proof, but the habit that keeps either alive is the same. This week, choose one route, add a single verb-first sentence above everything else in your notes, and begin from it the next time you sit down. Personal branding is mostly a long sequence of small restarts, and anything that makes each one cheaper is worth the thirty seconds it takes.








