Ideas for code review quality gates:
- no merge until you pass a quiz on the contents of your code and MR reviewer do as well
- no merge until user documentation is generated and developer documentation is generated (large code bases). This is waaay easier to read fast. `*`
- Actual code freezes where you stop writing code 4 days a week, except instead of depression, it is because the LLM wrote a month's worth of code on Monday.
Ask the LLM to review the code? An llm never just says lgtm, it writes a magazine article (paper artifact from the past that was 1-3 pages long, or about 8 vertical screen lengths) Now you got even more to read.
`*` (not talking about docstring documentation, I think that is slower to read start to finish, I mean, like user documentation except it talks about classes and modules, but not at a "just repeat the interfaces" level)
♡ 0 ↻ 0