rtdq

Why?

Dude, you're claiming that there's no likelihood of people getting swindled out of their money by handing it over to strangers. So your reaction is to play the bot card? We're done. You're clearly not arguing in good faith here.

What is bot logic exactly?

You keep describing this as not a likely or realistic scenario. But why is the likelihood even of relevance here? The way to avoid the worst case i.e scammed of your money, is to not even put it on the table in the first place.

I don't follow, and I'd be concerned that this opens up a cottage industry of bots generating plausible looking repositories that unwitting contributors would attempt to contribute to. We already know that bots are astroturfing repos to generate overinflated star counts. I'd say the least crap option here is to honeypot PR contributions from bots

The worst case is that someone loses out on $10, no? How does this work if the maintainer is the swindler?

> We're rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs to speed us up

Uh, if this is what I think it means, I wouldn't trust using a product where their company thinks that approvals for reviews can be automated.

Ask anyone who is a gamer what they think of AI. I guarantee you'll get a universally negative reaction because of RAMageddon.

There are two polar opposite vibes in this comment section: one guy above is calling FOMO, we should all get into the security trade, and yours is FUD.

I hope this all lands somewhere in the middle but honestly who knows at this point.

Pass, wasn't privy to the financials on this one.

What I do know is that for various reasons we struggled with direct hires and needed to grow quickly. So I guess the numbers somehow worked in its favour.

We ended up making use of hiring partners (basically consultancy companies) for this. They gave us access to a somewhat vetted candidate pool to interview from i.e. they could skip a tech test stage of an interview process.

Overall it has been a positive experience. It allowed us to scale up our engineering numbers relatively quickly. Potential cons to consider are the culture changes that come with it, the risk of outsourcing too much domain knowledge (direct vs. indirect hires) and potential time zone differences. It has also bought us time to focus on growing our direct hire count, which takes longer.