⬅️ GitOps Goes the World 🧭 There's A Lot of Opportunities ➡️

GitOps Down On It

June 11, 2023 by Jay Cuthrell

Share and discuss on LinkedIn or HN

Music: Kool & The Gang - “Get Down On It” (1981)

This week we take a look (again) at GitOps and the limits of Generative AI.

Last week we learned that the definition of GitOps was fluid.

https://fudge.org/archive/gitops-goes-the-world/

Today’s inspiration comes from antimetabole[^ antimetabole], chiasmus^[1], and an attempt to expend ~500 words. Also, I get to use Google Bard now that Google Workspace users can be enabled.

Get your back up off the wall 🎶

Until rhetorical flourish arrives via abundant VC funding and/or OpenGitOps, wordplay is harder than it looks. My best attempts are riffs on the _slow is smooth and smooth is fast_ military phrase:

Incomplete GitOps limits developers’ flow and an incomplete GitOps flow limits developers.

or…

Ruthless removal of annoyance results leads to GitOps and GitOps leads to reducing annoyances ruthlessly.

Sure, not my best, but they capture a baseline of my capability on a Sunday afternoon. Or as the saying goes…

Ploce^[2], but no cigar? 🤓

Now, let’s augment my _feeble_ human brain with Google Bard to see what it renders.

Explain GitOps using antimetabole or chiasmus as a rhetorical device.

Result:

Screenshot 2023-06-11 at 4.12.22 PM.png

_My completely off the cuff déjà vu search results theory_: Google Bard trained on artifacts from Sweagle around the time ServiceNow acquired Sweagle back in 2020. More research is needed with access to transparency reporting of Google Bard results.

Cause I heard all the people sayin 🎶

Granted, rhetoric driven definitions might be edge case for a marketing copy team queries. So, let’s simplify the prompt to Google Bard.

Where can I learn more about GitOps?

(_Note: I freely admit I am not an expert on prompting and I might be “holding it wrong”. My comments are in italics after the screenshot._)

Result:
Screenshot 2023-06-11 at 3.52.55 PM.png

_Nope. It was a link to ~3 year old podcast and the podcast art._
_Nope. It was a link to (FOSDEM) video recordings._
_Closer. It was a link to ~3 year old reference to a deleted GitHub repository._
_Solid listicle advice! But, no links._
_Solid listicle advice! But, no links._

Cosmetically, the results seemed promising until the click through. Again, more research is needed with access to transparency reporting of Google Bard results.

So, what will be the next big thing in GitOps and the limits of Generative AI?

Until then… Place your bets!