$ cat blog/why-this-devops-portfolio-exists.md
Why this DevOps portfolio exists
Why I am making the learning process public instead of waiting until I can present a polished end state.
I am not building this site because I already work as an experienced DevOps engineer. The point is almost the opposite: I am deliberately moving toward system administration, Linux and infrastructure, and I want the evidence of that transition to be visible while it is happening.
Context
My professional background is broad and practical. It includes application support, telecom and network infrastructure, data cabling, technical education support and many years of independent technical work. Troubleshooting, responsibility, communication and working with real constraints are familiar. Modern Linux infrastructure depth is what I am now building.
The question
There are two ways to make a portfolio. One is to wait until everything looks finished and then show only the final result. The other is to document the path: what I tried, what failed, which assumptions were wrong, what evidence changed my mind and how the system improved.
For this transition, the second approach is more useful. It demonstrates not only what currently works, but how I approach a system I do not yet fully understand.
What I want the site to show
- what I have actually built or investigated;
- which topics are current learning rather than claimed experience;
- how I use documentation and local evidence;
- how a hypothesis changes when the output contradicts it;
- how the homelab develops over time.
What I do not want it to become
This should not become a wall of technologies, generic AI-written tutorials or a performance of expertise. If I cannot explain a claim, reproduce an experiment or defend the reasoning, it should not be presented as evidence of competence.
Next step
The first public release runs on my existing hosting provider. That is deliberate: the website is useful now, while the infrastructure that will eventually host it becomes the next project.