Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
arcb
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
arcb
3mo ago
Thank you!
2.
▲
by
arcb
3mo ago
On re-read I think I might have overreached in my reply. I think having local LLMs being able run tool loops to _transform_ data, rather than just summary or analysis, will become 1/ great for non-technical users, 2/ fast.
3.
▲
by
arcb
3mo ago
We hear you on getting pulled into tarpit problems, and on the pattern you're describing leading to them. The core product motivation we're excited about is letting humans and their agents act on data together, but we do think tha
4.
▲
by
arcb
3mo ago
We're offering secure connections to sources like SQL DBs, warehouses, file stores, and MCP/API sources like PostHog or Salesforce. Customers can choose to set up credentials in our key store. We also support directly dropping dat
5.
▲
by
arcb
3mo ago
I suspect stronger edge performance will come as a side-effect of local inference. Your point on edge tool calls is interesting and I'll think about that. Features like offline mode could be a great motivating reason. Re knowing the sh
6.
▲
by
arcb
3mo ago
I hear you on fast responses. One of the frustrations I've had using BI / data tools in the past was not being able to get local performance... which led to me exporting data to spreadsheets or local code. We're taking this t
7.
▲
by
arcb
3mo ago
There are a lot of cool and useful things in there. What are you most excited about?
8.
▲
by
arcb
3mo ago
Not at the moment but it's in the queue. If there's a sign up method that works better for you feel free to DM me.
9.
▲
by
arcb
3mo ago
Thank you! If you try it out let us know how it goes!
10.
▲
by
arcb
3mo ago
Our outreach is vertical-specific, and healthcare is indeed on the list! But what we learned working a vertical is that the primitives underneath (shared queries, permissions, caching, refresh semantics) repeat across industries. We use Duc
11.
▲
Launch HN: BitBoard (YC P25) – Analytics Workspace for Agents
(bitboard.work)
58 points
by
arcb
3mo ago
|
25 comments
12.
▲
by
arcb
1y ago
I believe we will at some point. All question of the right need coming up. Text OCR has gotten really good, and if you think of it from a UI perspective, the only real contract is that a screen will show text that's representative of t
13.
▲
by
arcb
1y ago
It's a great repo! We had issues with iframes and framesets (which are old DOM tags) we had to write custom code for. Some DOMs need annotation to provide meaning to an LLM (for example, a button is clearly an "add demographics&qu
14.
▲
by
arcb
1y ago
We hope to be part of that brighter future! On the labor impact front, what we're seeing is that there is so much pent up demand for care, that any time we free up staff, they enable more throughput or more depth on casework. I hope
15.
▲
by
arcb
1y ago
I hear you. We constantly think of the value of clinicians' time. What could they be doing if they didn't have to do high-volume data entry. In one of our customers' cases, they instantly started helping doctors with respondi
16.
▲
by
arcb
1y ago
You might have seen this OSS logo in one of our videos: https://lucide.dev/icons/bot
17.
▲
by
arcb
1y ago
Great question. In the web agent case, we solely use HTTPS, and only between resources we either directly control (our servers), or whitelisted customer websites where we connect on HTTPS. An HTTP connection would fail the call stack, as wo
18.
▲
by
arcb
1y ago
Thank you! One of the big ones is that clinicians don't want more screens; they're already overloaded. So we're succeeding if we're invisible and yet effective for our customers. We're not dogmatic here - we can see
19.
▲
by
arcb
1y ago
We're looking to hire our first few engineers in the next few months, and we would love to talk to anyone who has an interest in working in this domain! If you'd like to talk more we're at founders at bitboard.work and are fa
20.
▲
by
arcb
1y ago
We don't use browser agents if an when we have an API - we prefer the strongest data types we can access. It comes down to what our customers can work with. Some of them are fairly technical (have an IT team), and some aren't (hav
21.
▲
by
arcb
1y ago
Thank you! We have a fork of browser-use that lets us hand hold web agents since we know our tasks are repetitive. We can cache expected paths and fire alerts if we go off the rails. We'd love to contribute it back at some point, mainl
22.
▲
by
arcb
1y ago
It depends on the source and destination. The trickiest case is when we're using browser agents for data entry. We can use the fact that we focus on repetitive tasks to our advantage - we know what sections of UI we need to check, and
23.
▲
by
arcb
1y ago
Thanks! From our side, we’re currently focused on specialty and multi-specialty groups. For example, obesity medicine, cardiology, pathology centers, radiology clinics... These groups tend to have repeatable workflows and a lot of operation
24.
▲
by
arcb
1y ago
Great questions. You're right that this is a high-stakes domain. Today, we only perform data entry in cases where we can deterministically verify that the information was correctly entered. Otherwise, we fail the task and flag it to th
25.
▲
Launch HN: BitBoard (YC P25) – AI agents for healthcare back-offices
63 points
by
arcb
1y ago
|
29 comments
26.
▲
by
arcb
2y ago
Incredibly motivating to read.
27.
▲
Managing the Bereaved
(findingbetter.substack.com)
2 points
by
arcb
2y ago
|
0 comments
28.
▲
by
arcb
11y ago
Sad to hear that - though that's the point :) There's so much pop culture around, deeper culture isn't appreciated as much. Check out our weekly archives: http://www.culturejoy.com/archives/ :)
29.
▲
by
arcb
11y ago
OP here, would love your thoughts!
30.
▲
Show HN: Culturejoy – Get cultured in 10 minutes a week
(culturejoy.com)
3 points
by
arcb
11y ago
|
3 comments
More ›