59 karma · joined October 10, 2014
it's more how can we make sure in the thousands of rows/changes that we are reviewing every day we don't have invisible issues while keeping the code standards we expect
You can use the agent from any client (web, Slack, Teams but also other harnesses).
We think most of data analytics work will be transformed (and is already being transformed) from SQL monkeys to chat to analyses, but all the UI/UX are not designed for this and this is what nao is, being open-source because knowing how the context is managed is key.
With nao you can have a conversation and then shared the output on the form of a story, that can be either static or live replacing what old dashboards were.
We are close to 1k stars on Github: https://github.com/getnao/nao
Nonetheless I like this policy as well.
With nao we are exploring the fact that agents are good to work with filesystems, so we help people getting the context into the filesystem and then you can plug our agent loop on top (on anything else).
The most exciting part is working with sandboxes and emulating filesystems. So at the moment the filesystem is local, but it could be a bucket or a database that we emulate as real filesystem for the agentic loop, all of this can also be mounted to sandboxes, and in the end you can do data transformations all in isolation with control on the context.
Nonetheless i like the idea.
Even though SQL as flaws, maybe a lot, it has one upside which is: it's so easy to onboard people on it, in the data ecosystem (warehousing etc.) it means that we can do way much stuff faster than before and hire less technical people, which is great
The ironic part of it is that most of the people doing 996 are building AI to replace humans work. And this is something that we don't talk about when speaking about 996. It's only a privilege, a lot of people would love to have normal job or a 996.
I come from Europe, I've had my high and lows when it comes to work hours, I was a consultant worked a lot, then a freelance and worked 2 day a week, now startup founder (YC) I don't count my hours but I'm close to working 6 days a week. To be honest the 4 years I worked 2 days a week were awesome and I'd wish everyone to reach that state where work is not the most important thing you do each week.
I really think what you showcase in the start of the article is the best thing, being able to statically highlight error in a text form for a user (or for a LLM) to iterate on the fixes is the best thing.
I'd love to know on what the semantic distance is computed. To make it more usable I'd love to be able to search for a company and see where in the graph it is, this way I could either look for my company or for a YC company that I know and then explore the proximity of this particular company.
Also I think we should be able to hover a dot to see the company