#1 -> part of scaling is you can't review every single line of code.

LLMs don't really scale if you're still the bottlneck, or they only scale as much as you reviewing every line of code - that's not that much scaling...

So I try to only review certain parts, like making sure they aren't changing tests to allow architecturally broken code to slip through (because they regularly try, even when given explicit instructions not to). Or if I'm watching them make changes on my phone and see that they are clearly doing the exact opposite of what they're supposed to be doing (regularly if I'm watching).

#2 -> if commits are small, GitHub's setup is good enough that you can review code on your phone.

#3 -> if they're huge, I can just review on my laptop at lunch or something.

Theoretically, all of this can be solved easily with orchestration and require minimal oversight.

If you're using LLMs to write code and you're carefully reviewing every line with a jade-handled magnifying glass, you're not really scaling - at least to the degree I'm interested in.