Introduction

Welcome to the November edition of "what we shipped". Luckily for our users, there are going to be three 🚀 ships this month because it was very hard to put everything together in a single place, 🤩.

In the last few weeks, the team has put in some ridiculous amount of work to enhance the developer experience in the Paradime Code IDE. Alongside, we have introduced new features in our CI/CD to help teams save costs during analytics development.

The overarching theme is we want analysts using Paradime to be 50%+ faster compared to other platforms. So without further ado, here it goes.

Code IDE

Run part of SQL

Paradime users can now select, compile, and preview data for a part of SQL in any model or CTE. Users can query any selection of a large dbt™ model and view the corresponding compiled SQL and data all from a single place. This has been an often-asked-for feature that teams needed to speed up their analytics game.

Copy filename as ref

A very useful productivity hack, especially if you have long file names. Users can right-click on a file in the file explorer and copy and paste the filename as ref. Users don't have to manually copy the filename or type it out in IDE anymore.

Lineage of any depth in the IDE

The lineage in the IDE always showed the first upstream and downstream nodes. To view the whole lineage, the user would have to navigate away from the IDE to the Lineage app. That's a context switch and users would have to do many back-and forth, adding friction to their development process. Well, not anymore.

In the Code IDE, users can now choose any or all node depths they want to see in the lineage. Users can independently choose the node depth upstream and downstream.

Users who have connected their BI, can also now see their entire cross-platform lineage during development in real time. For example, when one is developing or refactoring their dbt™ models, users will see the entire lineage all the way to their dashboards. They will be able to make informed decisions, shift-left the development process, and ship higher-quality, reliable code. More reliable code means less likely to break dashboards, less likely to create data incidents.

Merge conflict

Previously, the merge conflict experience on Paradime was kinda bad, like really bad. It was hard to see where the conflict was. Users would have to manually figure out where and what the conflict was. We are removing this pain point now.

We are shipping a whole new merge conflict experience at par with VS Code 🔥.

Users can clearly see what's in the current file vs what's coming from the branch the user is trying to merge. Users can also, in a single click accept changes from either branches or both and see the difference between branches too.

YAML validation

Working with YAML is a pain - not gonna lie. But it's an extra pain without any validation. Thankfully, YAML files provide a mechanism using JSON Schema to add validation so that users make fewer mistakes and get more real-time feedback. JSON Schema validation is now available across all dbt™ YAML files powered by the awesome schema developed by the dbt Labs™ team. The same kind of validation is also available for bolt schedules to ease the process of creating git-tracked schedules.

Switching to Git Lite and dark mode

Previously, switching between Git Lite and Git advanced or toggling light and dark modes was a pain as the settings were two levels deep. Users had to go through File menu > User preferences and then choose settings. We have gotten rid of all of those steps and now in a single click users can:

• Switch from git lite and git advanced
• Toggle on and off dark mode

Turbo CI/CD

In this release, Turbo CI is also getting a few impactful and much-needed upgrades around the life cycle of pull requests.

We have now modified the behavior of CI/CD so that:

• When a PR is raised in "draft", no CI checks are triggered
• When a PR moves from "draft" to "ready for review", CI checks are triggered
• When a PR moves from "ready for review" to "draft", CI checks are canceled
• When a commit is pushed into an "open" PR, existing CI checks are canceled

These changes are what our customers conceptually expect and also help save warehouse compute costs during analytics development.

Conclusion

The Paradime IDE experience is evolving rapidly. We are seeing users work 50 - 87% faster on Paradime compared to their previous experience on other platforms or in-house solutions. Teams using Paradime as a result are making a business impact and not wasting time on low-value work. In the next edition, we are going to share a few more updates that are making development faster on Paradime.