Hacker Newsnew | past | comments | ask | show | jobs | submit | wferrell's commentslogin

So...oai or google?


Yahoo. They're due for a comeback


Hey, maybe he has morals.


Really nice release. Excited to see this out in the wild and hopeful more companies leverage this for better end user privacy.


Not a public company.


Ah my mistake


@simonw

Great post. I've thought about what I want for better Vibe Engineering:

Each agent needs to deliver a fully working App/URL/Build so the functionality can be tested & verified.

Today AI IDEs deliver the diff + an explanation. Excellent. But give me the full build, a build I can share. A build that represents what it would be like shipped. When it comes to user facing functionality, a real build is how product owners verify a feature is complete.

Learn from Vercel -

A key part of Vercel’s magic is the automatic deployments for each branch. When working on a project with per branch vercel deployments - a team gets the immediate value of:

Shareable work - now others can see/test/give feedback on the great new feature you’ve developed - and their only work is to click a link (not git pull a branch and attempt to run locally)

No more “it works on my machine”. It either works or it doesn’t.

Confidence that if released, you know exactly what the user will experience. Give me automatic deployments for each agent, for each PR. And keep them available to spin up / re-use later.

I want to be able to re-launch it 3 months later and it just works. The reason we don’t do this today is the cost of the engineering - but with docker et al + AI agents, the cost of the eng work drops 99%

Deliver the deployment in such a way that immediate feedback to the AI could be given. This way minor tweaks can be executed immediately by the AI meaning that I can just wait for the minor tweak, review and then merge. This means the PR gets shipped NOW.


I think a key skill is knowing what level of complexity a single run can realistically achieve, which is often only a small task and not a fully working build.


Out of interest, what is the thinking behind sending a physical mailer to what feels like a large fraction of San Francisco?

Both why send it and why send it with very little info included on the page?


Did you get one? :) This was a part of our Series B raise to help get our name out


I did. Were you trying to get VCs to know about you? Or more like a twilio billboard that just said ask your devs?


The postcards were part of a dev-focused campaign to get people curious enough to check us out. We kept it minimal to stand out amongst other mail.


Wait, they sent out physical spam?


Nice André!


I wonder which customer triggered this…


Braze is my guess. They let customers do a lot of stuff with pushing and pulling data per user and I would guess every customer is in a sandbox. They were also impacted by the incident.


It sounds like anyone relying on Cloudflare and AWS us-east-1 were impacted. Not sure it's quite the smoking gun you're implying


It was the company that I found that was impacted and could have caused it. They also don't play nice with others. It's even in the documentation. We looked into buying their services. They have also caused load problems in other clouds. But it was just a guess. Could be anything.


Also curious if it was legit, misconfigured, or attack traffic.


Happy paying user of Chroma Cloud here. Congratulations Jeff, Hammad and team!

We were lucky to get early access and have saved a bundle.


I have 3 for our google cloud account and we spend like 5k a month.


They had an internal CRM. It was buggy, missing key features and engineers didn’t really want to work on it.


If I had jumped through Google's hiring hoops, I wouldn't either. Of course, this could be solved with money.


I think the real reason was there was no path to promotion for working on this. For better or worse the incentives were not aligned for great work to happen.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: