Hey HN, I'm Peter. We are building a code review tool and I wanted to know how the well-known engineers actually work with coding agents now (and how they review code) and not necessarily just what they say.
So I went through their repos, blogs, talks, tweets of 94 of them and made a card for each of them. Things like agents, models, harness, rules, skills, hooks and how they review whta their agent wrote. Agents did a lot of the digging, so every claim links to its source and you can check it yourself.
Most surprising finds are, that 8 of 94 still read every line of their code, and 21 more of them read the riskiest parts and skim the rest.
You can also make your own card (with your own agent), and it will suggest what trick from these 94 engineers you should try adapting.
If something is missing on a card, it means I didn't find it, not that they don't use it. If you spot something wrong, you can open a PR, happy to fix it.
Hey HN, I'm Peter. We are building a code review tool and I wanted to know how the well-known engineers actually work with coding agents now (and how they review code) and not necessarily just what they say.
So I went through their repos, blogs, talks, tweets of 94 of them and made a card for each of them. Things like agents, models, harness, rules, skills, hooks and how they review whta their agent wrote. Agents did a lot of the digging, so every claim links to its source and you can check it yourself.
Most surprising finds are, that 8 of 94 still read every line of their code, and 21 more of them read the riskiest parts and skim the rest.
You can also make your own card (with your own agent), and it will suggest what trick from these 94 engineers you should try adapting.
If something is missing on a card, it means I didn't find it, not that they don't use it. If you spot something wrong, you can open a PR, happy to fix it.