I had similar thoughts behind a tool I made (https://github.com/sshah03/perspica) on the concept, in that 1) reviews are now the bottleneck, and 2) we should be reviewing vs. intent. The difference was I endeavoured to make this process as easy for a human reviewer as possible, vs the automated approach here.
I would agree that the pace is getting too fast in some cases for human reviewers regardless of what tools are provided, in which case the solution discussed here is comparatively ideal. Possibly a state of mind I need to get over, but it feels risky if there's no one out there that has had eyes on code that goes in. Would you ever make a human understanding the change a fixture, or would that defeat the purpose of ZTHR?
Thanks for the reply!
I had a hard time with it, but if you can pass all the hardest checks and tests, it is writing better code than I can.
I think if the app is critical in a regulated industry then yes you can add back some human review at the final step, but have the AI also present all the fidnings to make that a fast job. if the blast radius is low, or the revert is 1 step, I would yolo!
Yes, pullsense.com is now parked. So, it would be hard to compare against that. But it did get announced here on HN, so you could at least check what was said about it.
But pullboard.dev was only recently announced on HN. So, you could do a compare and contrast with it. And same with rubberduck. And I’m sure that there are a bunch of other tools in this same space, which is why I would like to see a comparison of this sort.
You tell me that ZTHR is radically different from rubberduck, but I’d like to see a detailed comparison. And also against pullboard.dev. And any other tool in this space.
11 comments
[ 0.25 ms ] story [ 19.2 ms ] threadI would agree that the pace is getting too fast in some cases for human reviewers regardless of what tools are provided, in which case the solution discussed here is comparatively ideal. Possibly a state of mind I need to get over, but it feels risky if there's no one out there that has had eyes on code that goes in. Would you ever make a human understanding the change a fixture, or would that defeat the purpose of ZTHR?
I’m curious if anyone has done a comparison and contrast between all of these tools? How many others have I missed?
this is a zero code solution, not a better review tool.
But pullboard.dev was only recently announced on HN. So, you could do a compare and contrast with it. And same with rubberduck. And I’m sure that there are a bunch of other tools in this same space, which is why I would like to see a comparison of this sort.
You tell me that ZTHR is radically different from rubberduck, but I’d like to see a detailed comparison. And also against pullboard.dev. And any other tool in this space.