I've worked with data my entire career. We need to alt tab so much. What if we put it all on a canvas? Thats what I'm building with Kavla!

Right now working on a CLI that connects a user's local machine to a canvas via websockets. It's open source here: https://github.com/aleda145/kavla-cli

Next steps I want to do more stuff with agents. I have a feeling that the canvas is an awesome interace to see agents working.

Built with tldraw, duckdb and cloudflare

Scaling to zero with database persistence using litestream has cut my bill down to $0.1 per month for my backend+database.

Granted I still don't have that many users, and they get 200ms of extra latency if the backend needs to wake up. But it's nice to never have to worry about accidental costs!

Comments URL: https://news.ycombinator.com/item?id=47519540

Points: 4

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=47397329

Points: 4

# Comments: 0

I'm completely sold on the canvas layer. Embracing non linearity is such a boon when you're on the ideas stage. When you have verified it though, moving it to another medium (a document, presentation or just code) is often the best choice.

Do you see the canvases created with Spine as "one off" that you discard when you have got your deliverable, or as something living that you keep around?

I'm building a side project for running SQL on a canvas (kavla.dev), so I'm thinking about canvas workflows all the time!

Comments URL: https://news.ycombinator.com/item?id=47322911

Points: 1

# Comments: 0

I have worked with data for a while. I feel like our tools could be much better when it comes to "flow". I want an experience where you don't need to alt+tab to slack/images/another query. What if we put it all on a canvas? That's what Kavla is all about!

Since last month I've done a lot of improvements to the editor to make the "flow" better.

I've also read up on HMAC, Nonces and fun encryption stuff to create read only boards.

Here's one where I look at stack overflow survey for databases: https://app.kavla.dev/v/mqhg54o319doya4.67dbfee1ccd6caf638d3...

Snowflake users apparently make the most money!

Created a problem statement and then solved it with Gurobi, repo here: (https://github.com/aleda145/interview-scheduling-kontaktsamt...)

Agents feel like the perfect fit for the whole rescheduling loop that happens in the real world!

Have you had to use an optimization solver yet? If so, which one?

I don't know what to do.

Aside from the non-linearity, what key features would make you use Kavla instead of a notebook?

Is that something you're doing? What pain points do you have as interviewer with existing tools?

Great take on the SQL lock in, that's something that I need to think hard about. Ideally a git integration maybe?

Kavla also traverses the DAG, psuedo code:

  deps = getDeps() // recursive

  for dep in deps:
    if dep is query:
      run: "CREAT OR REPLACE VIEW {upstream} AS {upstream.text}
    if dep is source:
      done

Thanks for making me think about this!

What resource(s) are you using for learning SQL and DBA concepts?

I haven't really thought about Kavla as being a learning environment, maybe you are onto something!