A Pragmatic Way to Navigate the Cloud Native Wilderness

If you’ve ever opened the official CNCF Landscape, you probably felt that familiar mix of awe and overwhelm. With well over 1,000 projects, cards, and categories, keeping up with cloud-native tooling often feels impossible.

Over four years ago, while working at an IoT company (Vosker), my team hit that exact wall: We knew we weren't doing enough tech watch, but nobody had the extra bandwidth for dedicated research.

So we came up with a simple hack: We started naming our bi-weekly development sprints after tools from the CNCF landscape.

It began as a lightweight CLI utility that parsed the official CNCF landscape YAML file to pick a candidate tool every two weeks.

Whenever we planned a sprint, we took a couple of minutes to see what tool the sprint was named after. Even if we didn't end up using it in production that sprint, we heard the name, saw what category it lived in, and built continuous passive familiarity. Over months, that small routine turned into a surprisingly effective discovery habit.

Last winter, I revisited the concept. I missed that steady bi-weekly discovery cadence and wondered: Could I automate deeper curation using modern AI agents and LLMs?

Naturally, things escalated:

• I bought a domain name (cncf-landscape-a-to-z.com)
• Built a Hugo site and deterministic data pipelines
• Experimented with autonomous research agents (Pydantic AI, Jules, etc.) to generate summaries

Then reality kicked in: model API rate limits shifted, running naive agentic workflows with grounding attempts on a $0 budget was painfully slow, and maintenance quickly became a chore.

Nine months later, the realization hit: you don't need heavy AI pipelines or over-engineered autonomous agents to stay informed. A structured (maybe community-driven) watch list reviewed one letter at a time is far more valuable.

---

The 52-Week Plan: A to Z

To make the CNCF ecosystem bite-sized and approachable, I structured the journey across 52 weeks:

• Bi-Weekly Spotlights: I will publish an overview of CNCF landscape tools “starting with the letter _” every two weeks right here on Medium.
• Website Improvements: I’ll continue refining the companion site and open-source tooling over at https://cncf-landscape-a-to-z.com/
• Newsletter (Maybe): Eventually, I’d love to package this into an email digest — mostly so I can read it directly in my inbox without having to open my own site

---

How Do You Manage Tech Watch?

How does your team keep up with emerging tools in cloud native, DevOps, or platform engineering? Do you have your own sprint hacks or study habits?

Drop your thoughts in the comments! 👇