My Vision for RepoDB

I recently posted a Tweet laying out, unfiltered, where I want to take RepoDB. I wrote it myself, without any AI assistance, because I wanted it to come across exactly as I think about it.

I am expressing the full me here without the influence of AI.

Having extensive experience in .NET and being exposed to Python in recent years has given me a lot of thoughts about the possibilities of what humans can do with data. I also believe that data is the area where we can accelerate businesses and help AI learn even more from it.

IMHO, and don’t quote me on this, being in .NET alone is just not enough to understand the entire Enterprise ecosystem. One must really work with the different technologies and tools that Enterprise companies use and truly understand the pain points of the business.

I am using that experience to further improve the capabilities of my masterpiece (obra maestra), #RepoDB. As a hobby project that I work on during my nights and weekends, I am very committed to bringing this ORM library beyond being just another ORM in .NET. My goal is for it to become a developer productivity tool for everyone in this ecosystem.

Some of the capabilities are shown below, including Insights visibility and Default Telemetry. (Note: What I have shared here represents only the ideas currently in my head and capabilities that are already common in Enterprise corporations. There are many more functions to come.)

Imagine that John can do this across multiple database providers, while I am currently busy expanding the ORM to Oracle, Db2, MariaDB, Snowflake, Firebird, Vertica, and many more. Or imagine Claude or ChatGPT recommending and generating this small piece of code for you—code that delivers advanced capabilities many Enterprise teams struggle to build themselves.

#DotNet #CSharp #ORM #Data #Productivity #Tools

The context behind this Tweet comes from years of working in .NET while also being exposed to Python, which has shaped how I think about data and what it takes to truly serve the Enterprise ecosystem. It is not enough to be fluent in one stack; you have to sit with the different tools and technologies that Enterprise companies actually use to understand where the real pain points are. That is the perspective I keep bringing back into RepoDB.

RepoDB started, and remains, a hobby project I work on during my nights and weekends, but my ambition for it has grown well beyond being just another ORM for .NET. I want it to become a developer productivity tool, one that gives every developer in this ecosystem capabilities that are already standard in Enterprise corporations but rarely accessible in an open-source library. Insights visibility and Default Telemetry are two concrete examples of that direction, and they are only the beginning of what I have in mind.

This is also why expanding provider support to Oracle, Db2, MariaDB, Snowflake, Firebird, Vertica, and more matters so much to me right now. The goal is for these productivity capabilities to be available across the providers Enterprise teams actually rely on, not just a single database engine. And looking further ahead, I imagine a future where tools like Claude or ChatGPT can recommend and generate RepoDB code that delivers this kind of advanced capability out of the box, capability that many Enterprise teams currently struggle to build themselves.

More on this as it takes shape.