louisjoejordan

9 ms·

31.
by louisjoejordan 2y ago
Good choice!
32.
by louisjoejordan 2y ago
Fantastic work on this project—I'm really impressed! I have a quick question regarding the license: Since it's under AGPL, are there any specific limitations or considerations we should be aware of if we want to use this in our ow
33.
by louisjoejordan 2y ago
Thanks for your feedback - would love to know how I can do better next time. I definitely want to focus on improving substance next time - is there anything I can do to help with this? Admittedly I had to make the intro a bit clickbaity to
34.
Behind the YC Curtain – Raising $500k in 10 minutes(louisjordan.substack.com)
1 points by louisjoejordan 2y ago|3 comments
35.
by louisjoejordan 2y ago
Someone else added this as an issue! We're happy to take a look at it. To gage interest please upvote it :) https://github.com/quarylabs/quary/issues/4
36.
by louisjoejordan 2y ago
Hitting us with the hard questions! And honestly this is something people overlook about the realities of the data space. It's always easier to communicate what you are not, so let's begin there: - drag and drop query builder - ab
37.
by louisjoejordan 2y ago
That's useful feedback for us! We can improve our messaging. The simple answer is yes: Our focus is code first, from modeling to charts and dashboards, and not self-serve. We often found that keeping BI applications/dashboards or
38.
by louisjoejordan 2y ago
No sign in needed!
39.
by louisjoejordan 2y ago
From what I can see, OpenDashboard is tackling workflow automation tasks. We're more focused on the data modelling process.
40.
by louisjoejordan 2y ago
We're big fans of the Evidence team. While there's some overlap, we have a heavier focus on data modelling (similar to dbt). The key difference is we've rebuilt the modelling layer in Rust, leveraging WASM for better performa
41.
by louisjoejordan 2y ago
I think so too, will put this as a to-do.
42.
by louisjoejordan 2y ago
We've been focusing on the core VS Code extension and haven't released sharing yet. The plan is to provide a Vercel-like experience for deploying and sharing graphs. People will be able to connect their GitHub repositories, deploy
43.
by louisjoejordan 2y ago
Hey! We killed the auth flow from our extension, we used it to get an idea of how many people are using it. The extension works entirely local and connects to your database through your machine. So there's no need to self-host anything
44.
by louisjoejordan 2y ago
The biggest difference I see (though I'm not super familiar with Plotly) is that we define data transformations in SQL, while Plotly uses Python. One benefit of SQL is that it provides the advantage of tracing data lineage from source
45.
by louisjoejordan 2y ago
Appreciate your feedback and guidance. I was just at the Click-house office a few weeks ago - this is a really good idea.
46.
by louisjoejordan 2y ago
Great! Feel free to reach out to me with any questions.
47.
by louisjoejordan 2y ago
Appreciate the kind feedback! Curious to know if org-mode is still actively maintained.
48.
by louisjoejordan 2y ago
You're spot on that BI adoption is largely a social challenge. Our thesis is that by defining the entire journey from source to viz as code, we create a structured foundation that LLMs can build upon, democratizing access to the transf
49.
by louisjoejordan 2y ago
This is awesome! Great to see this project still alive after so many years :)
50.
by louisjoejordan 2y ago
Hey! OP here. This made my day, thank you!
51.
by louisjoejordan 2y ago
We do if you use DuckDB and you pull data from your data sources through DuckDB. DuckDB can act as a single interface between multiple data source types. Feel free to DM me with any more questions. around your specific use-case and I can he
52.
by louisjoejordan 2y ago
Hey! We love Redash too. Where Quary is different is that we have more of an emphasis on Transformation. This means people can split out complex SQL blocks into modular, reusable components which improves data lineage (how the data flows fr
53.
by louisjoejordan 2y ago
Hey! OP here. This is really good feedback thank you.
54.
by louisjoejordan 2y ago
Hey, great question ... Again another tool we love. A few key differences: - Visual studio code as the editor through and through - Dashboards are fully defined in code Quary which is different to Rill - At its core our architecture is also
55.
by louisjoejordan 2y ago
Big fans of our fellow YC mates at Lightdash! There are some core differences that make our product feel quite different: - Lightdash isn't Lightdash without dbt so you always have that divide even though they have done a fab job of mi
56.
by louisjoejordan 2y ago
Hey! OP here, I don't have a clear answer for this yet. We're exploring ways to make Quary more extensible. We are focusing on the core piece first, happy to chat to hear more about your specific use-case.
57.
by louisjoejordan 2y ago
Hey! Thanks so much, really appreciate the feedback
58.
by louisjoejordan 2y ago
Hey, OP here. We love what dbt has done for transformation-layer engineering. But we often see companies still struggling with a mess of unstructured dashboards, even with solid dbt models underneath. The problem is that dbt models and BI d
59.
Show HN: Open-source BI and analytics for engineers(github.com)
293 points by louisjoejordan 2y ago|75 comments
60.
A portable SQL linter (rust)(github.com)
2 points by louisjoejordan 3y ago|2 comments

More ›