Skip to content

Update README with agentic positioning and vibe coding rationale #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shuveb merged 1 commit into from
Apr 16, 2026
Merged

Update README with agentic positioning and vibe coding rationale #63

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@
</p>

<p align="center">
<strong>Modern, Pythonic Data Transforms</strong><br />
Build data transformation pipelines using Python — with a visual IDE and AI assistant.
<strong>Agentic &amp; No-Code Data Transformations</strong><br />
Vibe coded pipelines: say hello to accuracy and maintainability.

@greptile-apps greptile-apps Bot Apr 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Ambiguous tagline phrasing

"Vibe coded pipelines: say hello to accuracy and maintainability." reads as though vibe-coded pipelines are the subject greeting accuracy/maintainability, which inadvertently frames vibe coding positively — the opposite of the cautionary angle in the body text. A clearer phrasing would make the benefit explicit.

Suggested change
Vibe coded pipelines: say hello to accuracy and maintainability.
Vibe coding your pipelines? Say hello to accuracy and maintainability.
Prompt To Fix With AI 
This is a comment left during a code review.
Path: README.md
Line: 11

Comment:
**Ambiguous tagline phrasing**

"Vibe coded pipelines: say hello to accuracy and maintainability." reads as though vibe-coded pipelines are the subject greeting accuracy/maintainability, which inadvertently frames vibe coding positively — the opposite of the cautionary angle in the body text. A clearer phrasing would make the benefit explicit.

```suggestion
  Vibe coding your pipelines? Say hello to accuracy and maintainability.
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code

</p>

<p align="center">
Expand All @@ -33,7 +33,12 @@

## What is Visitran?

Visitran is an **open-source** data transformation tool that supports **no-code** (visual drag-and-drop) and **AI-assisted** (natural language) approaches to data modeling. It connects to your data warehouse, lets you build transformation pipelines visually or by describing what you need in plain English — and materializes results back to your database.
Visitran is the modern, agent-native data transformation platform that lets you create sophisticated, yet highly standardized transformation metrics and highly maintainable transformation projects with AI. It is built on a strong foundation of Python (powered by Ibis) and SQL, while affording you a simple, conversational interface.

### I just vibe code my pipelines. Why do I need Visitran?

First off, congratulations. You are using modern tools to quickly solve pains you have. The trouble starts when everyone in your organization is vibe coding pipelines and seeing different numbers for critical metrics. Pandemonium ensues. As it is, it's tough for even humans to come to an agreement on how core metrics are defined. With Visitran, you get the best of both worlds. You "vibe code" your pipelines with Visitran AI, but you can collaborate with your team members and build transformations that are agreed upon, verifiable and maintainable. Speed: say hi to accuracy. Accuracy: say hi to maintainability.

@greptile-apps greptile-apps Bot Apr 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Closing slogan implies trading off, not adding

"Speed: say hi to accuracy. Accuracy: say hi to maintainability." reads as a sequential replacement — speed gives way to accuracy, which then gives way to maintainability — suggesting you lose each quality as you gain the next. The intent appears to be that Visitran delivers all three simultaneously. Consider a phrasing that conveys addition rather than substitution, e.g. "Speed without sacrificing accuracy or maintainability."

Prompt To Fix With AI 
This is a comment left during a code review.
Path: README.md
Line: 40

Comment:
**Closing slogan implies trading off, not adding**

"Speed: say hi to accuracy. Accuracy: say hi to maintainability." reads as a sequential replacement — speed gives way to accuracy, which then gives way to maintainability — suggesting you lose each quality as you gain the next. The intent appears to be that Visitran delivers all three simultaneously. Consider a phrasing that conveys addition rather than substitution, e.g. "Speed without sacrificing accuracy or maintainability."

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code



**Supported Databases**

Expand All @@ -48,14 +53,14 @@ Visitran is an **open-source** data transformation tool that supports **no-code*
## Key Features

**For Data Engineers**
- Full Python-based transformation models with Ibis SQL generation
- No-code backed by Python-based transformation models with Ibis SQL generation

@greptile-apps greptile-apps Bot Apr 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Awkward feature bullet for Data Engineers section

"No-code backed by Python-based transformation models…" is odd wording in a Data Engineers feature list. "Backed by" places no-code as the primary attribute with Python as the supporting layer, which is the reverse priority for this audience. The removed original ("Full Python-based transformation models with Ibis SQL generation") communicated more clearly to engineers.

Suggested change
- No-code backed by Python-based transformation models with Ibis SQL generation
- Full Python-based transformation models with Ibis SQL generation
Prompt To Fix With AI 
This is a comment left during a code review.
Path: README.md
Line: 56

Comment:
**Awkward feature bullet for Data Engineers section**

"No-code backed by Python-based transformation models…" is odd wording in a *Data Engineers* feature list. "Backed by" places no-code as the primary attribute with Python as the supporting layer, which is the reverse priority for this audience. The removed original ("Full Python-based transformation models with Ibis SQL generation") communicated more clearly to engineers.

```suggestion
- Full Python-based transformation models with Ibis SQL generation
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code

- 6 database adapters with table, view, and incremental materialization
- DAG execution engine with dependency resolution
- Job scheduling with cron/interval triggers, retry, and chaining

**For Analysts & No-Code Users**
- Visual IDE with Monaco editor, file explorer, and DAG visualization
- No-code model builder — joins, filters, aggregates, window functions, pivots, unions
- Formula Columns support: Create complex transformations with Excel-like formulas
- AI assistant for natural language to data transformations
Comment on lines 61 to 64

@greptile-apps greptile-apps Bot Apr 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Removed concrete IDE feature details

The line "Visual IDE with Monaco editor, file explorer, and DAG visualization" was dropped from the Analysts & No-Code Users section. This was one of the most concrete, scannable differentiators for that audience (Monaco editor and DAG visualization are recognizable signals of quality). Replacing it only with Formula Columns leaves the section lighter on tool specifics for non-technical readers who need more context to evaluate the product.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: README.md
Line: 61-64

Comment:
**Removed concrete IDE feature details**

The line "Visual IDE with Monaco editor, file explorer, and DAG visualization" was dropped from the Analysts & No-Code Users section. This was one of the most concrete, scannable differentiators for that audience (Monaco editor and DAG visualization are recognizable signals of quality). Replacing it only with Formula Columns leaves the section lighter on tool specifics for non-technical readers who need more context to evaluate the product.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code

- Built-in testing framework for model validation

Expand Down
Loading