Load-Bearing https://tilvids.com/c/loadbearing_channel/videos A load-bearing wall is the one you can't take out. Everything above it depends on it holding. Software has those too: the decisions everything else is built on. If you build software and want to understand it all the way down, this is Load-Bearing. For engineers who want to reason about systems, not just build them. New videos when there's something worth saying. Writing and case studies at builtbythanh.com. Mon, 12 Oct 2026 15:17:44 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://tilvids.com Load-Bearing https://tilvids.com/lazy-static/avatars/312e87ea-8857-469e-8bc8-02ef9a9a473b.png https://tilvids.com/c/loadbearing_channel/videos All rights reserved, unless otherwise specified in the terms specified at https://tilvids.com/about and potential licenses granted by each content's rightholder. https://tilvids.com/feeds/podcast/videos.xml?videoChannelId=12221 <![CDATA[Your Code Review Bottleneck Isn’t What You Think]]> https://tilvids.com/w/2irfRmkwSjEWYxd6XU4PKK https://tilvids.com/w/2irfRmkwSjEWYxd6XU4PKK Mon, 12 Oct 2026 10:58:20 GMT Your teammate builds a feature with AI in 20 minutes. Then you spend the afternoon working out what it does. Are you becoming the bottleneck?

I think that question hides two different problems: the amount of code coming at reviewers, and the understanding that hasn't happened before the code reaches them. They need different fixes. In this video, I use one example (a spreadsheet import that quietly brings back an old phone number) to show what understanding a code change actually involves, and end with two things to try on your next few pull requests.

Chapters
0:00 Am I the bottleneck?
0:50 Two sources of review burden
2:27 What understanding a code change involves
4:04 When the author understands the code
6:18 Making the volume manageable
7:52 Using AI to build understanding
9:17 What to try on your next PR

Sources

Asdaque et al., "Novice Developers Produce Larger Review Overhead for Project Maintainers while Vibe Coding" (arXiv, 2026): https://arxiv.org/abs/2602.23905
LLVM AI Tool Use Policy: https://llvm.org/docs/AIToolPolicy.html
Google Engineering Practices, Small CLs: https://google.github.io/eng-practices/review/developer/small-cls.html
Anthropic, "How AI assistance impacts the formation of coding skills" (2026): https://www.anthropic.com/research/AI-assistance-coding-skills

If you're an author: before your next pull request, ask yourself whether you could help someone reason through what the code will do. If you're a reviewer: what's actually taking your time? Tell me in the comments.

]]> Load-Bearing Science & Technology nonadult Your Code Review Bottleneck Isn’t What You Think Your teammate builds a feature with AI in 20 minutes. Then you spend the afternoon working out what it does. Are you becoming the bottleneck? I think that question hides two different problems: the amount of code coming at reviewers, and the un...