Did exactly that for the actual filing — Python, mentioned in the post. The 23 numbers were a probe, not the goal: I wanted to understand how it works.
Probably momentum. It takes some effort to change tooling. This is why Cursor worked so well in the beginning. It just took over from VSCode seamlessly.
Hi, we have been working on a personal assistant for knowledge professionals. A lot of challenges around building an advanced RAG, improving reasoning, and custom models
Rappo | https://buildrappo.com | Founding Fullstack Engineers | Remote (Preferably India)
Hi, I am the founder of Rappo (agentic GTM Chief of Staff). We observed that technical startups spend way too much time in the early stages figuring out GTM.
Everyone says early PMF is crucial, but there is no streamlined support there.
This is amazing overview of the current challenges.
As a database practitioner and a founder of a database startup, I would be curious to see how you approach these challenges and address them. Also, how you make it economically sustainable too.
Thanks, really appreciate the feedback - we’re tackling this by moving away from the old “pipeline for every problem” mindset. Instead, we built a mesh that connects all your databases—regardless of tech or location. With our unified model, we can handle access, migrations, replications, and even obfuscation. The model understands schemas across different types of databases and provides version control.
On the sustainability side, we don’t sell services or ETL tooling. We license the core platform like you would a service mesh or gateway. It’s meant to be scalable, reduce tool sprawl, and cut down on all the manual stuff teams usually have to maintain. The goal is to make modern data infrastructure both smarter and lighter to run.
reply