Chroma is the open-source search database for AI applications. It supports dense vector, sparse vector, regex, and full-text search. We support local, single-node, and cloud hosting.
We're a team of 14, all engineers today. We work in Rust, Python, Typescript, and Go.
I was curious what the break-even is where the insurance discount covers the $99/mo FSD subscription. I got a Lemonade quote around $240/mo (12k mi/yr lease on a Model 3), so 50% off would save ~$120/mo - i.e. it would cover FSD and still leave ~$21/mo net. Or, "free FSD is you use it".
I believe, at the end of the day, insurance companies will be the ones driving FSD adoption. The media will sensationalize the outlier issues of FSD software, but insurance companies will set the incentives for humans to stop driving.
I don't have a car so I don't know what is normal. i just went through the lemonade quote process. (I have a license and my record is clean, though - so there shouldn't be any high-risk flags.)
Yep, also people who will spend thousands of dollars to get a tiny scratch repaired because for some reaosn in the US everyone expects cars to be utterly perfect.
Yep - the way to get adoption, whilst the bar is too high for self-driving cars, the bar should be safer than the average person. An old greying socialist - saying that capitalism drive the right outcomes. Same with low-carbon, insurance will help with climate change mitigation.
How many people are stuck in the middle, having less extreme beliefs reinforced by a sycophantic AI?
I've started to hear whispers among friends that there are many founders stuck in loops of "planning" with AI, reinforcing banal beliefs and creating schizophrenia-like symptoms.
This is cool, but Claude for Chrome seems broken - authentication doesn't work and there's a slew of recent reviews on the Chrome extension mentioning it.
Sharing here in case anybody from Anthropic sees and can help get this working again.
It may seem off-topic, but I think it hurts developer trust to launch new apps while old ones are busted.
This is cool, but does everybody have enough work for multiple agents in parallel?
I feel like I'm limited by writing specs for agents, then by reviewing their work.
I typically spend 30-60 minutes writing a spec, then the agent runs for 30-60 minutes, then I spend 30-60 minutes refining code/ui/etc before putting up a PR, then another 30-60 minutes waiting for CI + addressing automated + human code review feedback.
I find if a project is made with agentic coding in mind, you can try to implement features as they come to mind and bounce between different CC terminals.
The problem is that this is true of none of my work projects and the onboarding cliff to agentic coding is quite steep. I have to use discretion to apply CC when it does make sense, which is not that often.
I'll have claude code editing a script on my laptop and another on the VM running it and synthesizing the results. Then sometimes I'll have another doing some odd job or researching something. Then I'll pull up gemini in my browser to figure out what I should make for lunch...
I usually use one instance, sometimes two. But this is a reasonable account of Chris Rackaukas using 32 instances at a time to do boilerplate maintenance across a bunch of open source repositories: https://www.stochasticlifestyle.com/claude-code-in-scientifi...
> I have had to spend like 4am-10am every morning Sunday through Saturday for the last 10 years on this stuff before the day gets started just to keep up on the “simple stuff” for the hundreds of repos I maintain. And this neverending chunk of “meh” stuff is exactly what it seems fit to do. So now I just let the 32 bots run wild on it and get straight to the real work, and it’s a gamechanger.
Chroma is the open-source search and retrieval database for AI applications. It supports dense vector, sparse vector, regex, and full-text search. We support local, single-node, and cloud hosting.
We're a team of 14, all engineers today. We work in Rust, Python, Typescript, and Go.
reply