Where I'm headed and what's next
Understanding and documenting how Kyverno enables platform engineering and governance at scale.
Building comprehensive relationship definitions and cloud native architecture patterns.
Creating comprehensive plugin development guide and improving docs experience.
At least 2-3 meaningful PRs per project. Build credibility and understanding.
Document my understanding of each project's architecture and use cases.
Become known as someone reliable and thoughtful in these communities.
Share learnings from contributions. Help others understand these projects.
Most people choose: code XOR docs. I want to do both well.
My goal is to become known as someone who:
Open source projects need people who can bridge the gap between builders and users. Good documentation isn't just nice-to-have—it's critical infrastructure that multiplies the impact of code.
Getting work merged means maintainers trust my contributions. This is the ultimate validation.
Positive reviews and comments that show I'm solving real problems.
Receiving minimal review requests. Clean, thoughtful code that needs few changes.
Other contributors finding my docs useful. Issues and discussions citing my work.
Understanding deeper technical concepts. Becoming more confident in complex systems.
Invitations to contribute, speak, or work on open source professionally.
If you're interested in open source, technical writing, or building in public, let's connect.