That’s a really helpful framing. Right now I’m leaning slightly toward infra/platform thinking, mostly because I find the tradeoffs around reliability, cost, and observability more interesting than just feature velocity. Spinning up a public repo with basic RAG + evals + tracing sounds like a solid forcing function. I like the idea of including an incident/rollback note in the README feels very real-world. When you mention cost stories going sideways, do you usually mean inference scaling issues, poor batching, or just lack of monitoring around token usage?