pull down to refresh

I'm interested in this approach, my main use of LLMs are in tech-specific use-cases. I have specific Spaces in Perplexity for things like "Ansible EDA (Event Driven Architecture)", etc.
My point is its hard to frame very tech specific conversations within a "multiple persona" lens because ultimately all personas need to know and advocate for the specific tech involved.
However I imagine what you could do is have say 3 Personas:
  1. GitOps true believer - he sees that every single problem can be solved by prodigious use of git-driven automation scenarios. Git is the ultimate "source of truth" and its benefits almost always outweigh the complexities it brings.
  2. The balanced view. Automation must always be serving actual real pain points, its pointless to rely too much on automating things that are either so rare, so minor, or so specific that the complexity cost outweigh the gains. Use of GitOps automation must always be providing actual measurable gains in efficiency. The final result must be a SIMPLER system, not more complex.
  3. The doubter. They aren't anti-GitOps far from it. They are a 10 year veteran of the space. But they have seen enough of the promises not be fulfilled to understand that its never a solution to all problems. They will argue it introduces lots of latency, lots of sluggishness, and as systems grow larger and larger everything just becomes more unresponsive. They generally advocate for a "surgical use" of gitops. Usually very specific and narrow cases were its clearly the best answer.