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.
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
Migrate to Jupyter fork with AI features #76
Conversation
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
a2a767e
to
cd9e244
Compare
Co-authored-by: Ramon Garate <ramon@withpretzel.com>
…to fix-error-with-ai
…to fix-error-with-ai
…to fix-error-with-ai
Our goal with Pretzel AI is to make the best tool for all data use-cases. This means many things: a great visual/AI enabled data exploration, a great SQL IDE, a great collaborative data workspace, an visually amazing dashboard and many more things.
We needed some place to start. We tried to make a visual and AI enabled data exploration tool that runs completely in the browser. We soon realized the challenge with this - it's very hard to get data professionals to switch with this approach. Why does that matter? In our opinion, to create change in an established space, you need to convert people who are the most passionate first. These users drive the change.
For us, that means targeting data scientists, analysts, research, ML engineers and people who work with data every single day and find their existing tools lacking. This means focusing on improving the tool that these power users use - Jupyter.
We could've made a new notebook tool from the ground up but we decided not to - switching costs are a thing and we want to make it extremely easy to switch. So, we chose to fork Jupyter and add features to it.
I'll cover more details in a blogpost at some point on each of these points but for now, here's the PR that merges our first major change - adding native AI code gen features in Jupyter