Hey Prophecy Community, happy fun Friday! This week, I’m asking:
How do you feel about the term “vibe analysis?” Like vibe coding, but for data prep and analysis.
Respond by reacting to this post with an emoji to indicate your thoughts! Or, of course, you can comment below with your opinion 
p.s. if you doubt anyone uses this term, check out this interesting essay on vibe analysis from last summer: Vibe Analysis - by Dan Hockenmaier - Dan Hock's Essays
Great post @MeganBowers I am really keen to hear other people’s opinions..
Personally I love the term “vibe analysis.” One thing the (excellent) article you linked misses is the collaboration, repeatability, and auditability aspects of building pipelines (governance, if I had to distill it into a single word.)
While it’s great that everyone is enabled to “have at it” and build logic for their own analysis needs, from an enterprise lens, collaboration and auditability matters.
From a collaboration perspective, I see two problems emerge: first, not everyone will be aware of what others are building, limiting opportunities to collaborate. Second, the creators of these solutions aren’t necessarily looking to collaborate, at best, they’ll upload their code to a private Git repo to gather dust; at worst, they’ll save it in a non-versioned folder on their desktop. Keen to hear thoughts on this of course!!
Back to the article… As a Prophecy employee, and working with Prophecy customers, I am most excited by two things:
@Callum_Finlayson I am also excited by the idea of making “vibe analysis” governable. I think the auditability piece is the biggest one – just like with vibe coding, businesses need to verify that the code produced by AI agents is correct.