"Open source has always worked on a system of trust and verify"
Not sure about the trust part. Ideally, you can evaluate the change on its own.
In my experience, I immediately know whether I want to close or merge a PR within a few seconds, and the hard part is writing the response to close it such that they don't come back again with the same stuff.
Cool to see you here on HN! I just discovered the openpilot repository a few days ago and am having a great time digging through the codebase to learn how it all works. Msgq/cereal, Params, visionipc, the whole log message system in general. Some very interesting stuff in there.
trust resudes the verification I suppose. Getting a PR from a trusted contributor would probably have me do a quick scan for obvious mistakes. And they'd know to keep the PR's small and on the right branch to help facilitate a scan.
a new person with a big idea on the slightly wrong (but reasonable) channel would have more work in verification.
Why? I don't appreciate comments that cast doubt on decent technical contributors without any substance to back it up. It's a cheap shot from anonymity.
Sounds like you misunderstood. They didn't say they are merging PRs after a few seconds. Just that the difference between a good one and a bad is often obvious after a few seconds. Edit: typos
What kind of things would you like to hear? The default is you hear nothing. Most black boxes work this way. And you similarly have no say in the matter.
This was back around 2017-19 (can't remember the exact year), but it was definetly pre-Covid and left a bad taste in my mouth, just like Jane Street and FTX at the time - especially given that your then competitor Deepscale didn't have that style of interview.
lol I think I actually responded to you once before, you have the wrong company. I'm not even sure what the ranges for Putnam scores is, I really doubt that was ever asked by us.
roughly speaking, the latest policy models trained in it are indistinguishable from openpilot release on 15-30 mins of driving, but you start to notice the subtle issues (e.g. turn cutting) on a few hours of driving.
we'll definitely do some good writeups and/or talks once it's shipped.
comma.ai | Software + Hardware Engineers | San Diego, CA | ONSITE
Our mission is to solve self driving cars while delivering shippable intermediaries. We build and sell the comma 3X to a growing fleet of users and get back 3M minutes of driving data every week for training openpilot.
Not sure about the trust part. Ideally, you can evaluate the change on its own.
In my experience, I immediately know whether I want to close or merge a PR within a few seconds, and the hard part is writing the response to close it such that they don't come back again with the same stuff.
(I review a lot of PRs for openpilot - https://github.com/commaai/openpilot)