mikesurowiec

From the full announcement

> The new classifier also comes at the cost of flagging benign requests more often during routine coding and debugging tasks. As with all our safeguards, we’ll continue to refine this to better distinguish genuine misuse from legitimate requests and reduce false positives.

When I saw this, I thought it was a paid advertisement on HN. yuck. At least when other companies do the jobs post it always includes "is hiring" to make it clear what it's for.

I worked on docs at GitHub which are open source, synced to an internal repo, and deployed on internal infra. I recall jumping through many hoops to make it work safely. These were workflows that had secrets access for deployments, and I recall zipping files, doing some weird handoffs/file filtering between different workflows based on the triggers and permissions. Security folks were really quick to find any gaps =)

Glad to see a few more security knobs on actions these days!

I expect data centers will become more expensive precisely because everyone is building at the same time. Supply chain crunch

I’ve seen people spin Results in their favor within a company, where you can validate them, but for interviews it seems nearly impossible to validate.

Does anyone have techniques for that?

You're absolutely right, apologies!

Is this the same reason you wouldn’t pick up trash on the floor?

Relative speed difference is another key factor — arguably more important than absolute speed — but is more difficult to regulate.

When traffic on the highway is near a standstill you really shouldn’t fly down an open lane at the highway speed limit

The post states "they used Cap’n Proto before they hired me"