Luis Artol
An engineering lead at Google Maps who focuses on the substantive impact of AI programming on the efficiency of feature delivery.
Timeline (last 90 days)
Google Maps' Luis Artol pointed out that the key question is "are we delivering features faster, or just delivering code faster," and that early signals suggest faster feature delivery is happening, but the way it is measured is completely different from counting PRs.
Luis Artol proposed distinguishing between "good friction" and "bad friction," arguing that code review is "good friction," and that the path is to use AI to improve the quality of upstream inputs (architecture understanding, specifications) so that review goes more smoothly, rather than eliminating review.
All Facts (2)
Google Maps' Luis Artol pointed out that the key question is "are we delivering features faster, or just delivering code faster," and that early signals suggest faster feature delivery is happening, but the way it is measured is completely different from counting PRs.
50%UnverifiedLuis Artol proposed distinguishing between "good friction" and "bad friction," arguing that code review is "good friction," and that the path is to use AI to improve the quality of upstream inputs (architecture understanding, specifications) so that review goes more smoothly, rather than eliminating review.
50%