Viktor Farcic Portfolio
His GitHub shows the DevOps Toolkit book/course series alongside real repos — docker-flow-proxy (596 stars), k8s-specs (164 stars), and dot-ai, a newer TypeScript-based Kubernetes agent for plain-English cluster deployment.
What makes it work
A breakdown of the choices that make this portfolio stand out.
A GitHub history spanning old Docker-era tools to a current AI-agent project
docker-flow-proxy dates from the early Docker Swarm era; dot-ai is a 2025-era LLM-driven Kubernetes deployment agent. Having both visible shows continuous adaptation across roughly a decade of infrastructure-tooling shifts.
Star counts that reflect real, sustained adoption
Hundreds of stars accumulated over years on infrastructure-automation repos is a signal other engineers actually pulled the code into their own pipelines.
A book/course series used as the connective narrative
The DevOps Toolkit series ties individual repos into a coherent teaching arc, turning a scattered set of side projects into a legible body of work.
What DevOps Engineers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Keep old, once-popular repos visible even after you've moved on technically — the range shows adaptability.
Let star/fork counts on real infrastructure tools carry the credibility instead of describing yourself as an "expert."
If you have several related repos, tie them together with a book, course, or blog series that explains how they connect.
More DevOps Engineer portfolios
Ready to build your portfolio?
Follow the DevOps Engineer roadmap — skills, projects, and timeline to get hired.