Recent submissions

Comment · 3 months ago
We assume LLMs can always be fooled, so the judge is just one step of the verification process. The deterministic layers, per-tool db roles, read-only-by-default integrations, query timeouts, are the ones an admin can configure. The judge's rules aren't exposed to admins today. I like your idea of letting admins add their own rules or knowledge to the judge, we should add that.
Comment · 3 months ago
Yes, we support Snowflake and ClickHouse today. And we're happy to integrate more, just say the word :)
Comment · 3 months ago
Thank you! Yes, you can share it externally if it isn't connected to external data sources.
Comment · 3 months ago
Thanks! We believe the building aspect is already commoditized and we're experimenting with leaning into this with BYOA (bring-your-own-agent). Our bet is that the labs will stay focused on the model and won't do the more unglamorous governed deployment layer needs (credential scoping, per-tool db, audit, etc), but time will tell.
Comment · 3 months ago
Thanks! We've actually have been experimenting with the config generation approach as well. One tradeoff we noticed was it turns the system into more of an app builder where the ceiling of what you can do is lower compared to a coding agent. But it's much faster than codegen. How dynamic have you found Lowdefy compared to codegen?
Comment · 3 months ago
Thanks! Agree that for one-off questions, chat is the right interface. We’ve found apps win when the workflow is repeated across a team and they almost become “templates” that seed ideas for other coworkers.
Comment · 7 months ago
Hey! I built this because everyone's writing CLAUDE.md files now but nobody knows if theirs actually works. The research is contradictory too, one paper says they hurt performance, another says they help. So I made a tool that just measures it on your own repo using your own PRs and your own test suite.

Turns out it's not often you can point to a single markdown file and say "this made the agent 27% better at resolving real tasks." That's what we saw on our production monorepo. I imagine this as a way for teams to actually make their agents write better code instead of guessing.

Comment · 1 year ago
Yes it's based on the position. The column determines the note and the row determines the octave.
Comment · 1 year ago
If you try turning your phone off silent it should work!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton