In a world where LLMs have become a central part of our toolchains, we as an industry are at a crossroads of figuring out how to best leverage non-deterministic systems for deterministic outcomes. In my recent experience, the best way to make LLM's have more useful output is to provide just the right amount of context for an audit, feature development, or any other ask. In trying to best encompass the complexity of the many layers of systems from network to services to data, I envisioned and implemented a complex, dynamic architecture diagram and schema that our LLMs could use with skills to better assist our product developers in how we understand new feature development, cross-service constraints, data lineage, and more.
Rainu is a web dev turned data engineer turned infrastructure engineer. She's spent time all across the stack and just kept digging back to the absolute infrastructure. She's been a tech lead on and off for the past 4 years, and in that time…
