ClaireGz

4 ms·

1. 31.▲
   by ClaireGz 1y ago

   Great! Let us know if it's how you imagined it when you try it
2. 32.▲
   by ClaireGz 1y ago

   Thanks for the kind comments, he's surely a great guy :)
3. 33.▲
   by ClaireGz 1y ago

   When it comes to SQL writing we are more relevant, when it comes to speed this is hard to benchmark exactly against Cursor and Windsurf but we are a bit slower (around ~600ms on average) obviously and we know what we have to improve to spee
4. 34.▲
   by ClaireGz 1y ago

   Thank you! Actually this is exactly what we target, we've seen that data teams have often a longer feedback loop than software engineers. That's a goal for us to shorten it and to bring data the closest to your dev flow.
5. 35.▲
   by ClaireGz 1y ago

   For the joins, we give the right context so that the model can infer the relationships: the schema of each table + how the joins are already done in your repository/query history. Usage analysis is definitely on the roadmap: we want to
6. 36.▲
   by ClaireGz 1y ago

   Yes it's in our roadmap, some users already asked for it!
7. 37.▲
   by ClaireGz 1y ago

   Yes we use Fill in the middle models (Mistral and our own trained Qwen). And we feed it with your data context - we have our own SQL parser to feed you with the right data schema context depending on where your cursor is in the query.
8. 38.▲
   Launch HN: Nao Labs (YC X25) – Cursor for Data

   158 points by ClaireGz 1y ago|64 comments