Code Quality — The Video Signal

Sep 10, 2026 · 25:56

Tessl Code Review: Catching 74% of Bugs Pre-Merge

Tessl Code Review is an AI-native code reviewer designed to address the critical bottleneck of trusting code generated by coding agents in a software factory. It functions as an automated GitHub app that runs specialized, customizable review rules (lenses) against Pull Requests (PRs). The system emphasizes self-improvement loops, allowing the review process to learn from the codebase and the team's specific best practices, thereby increasing defect detection rates (claiming up to 74% detection).

Key takeaways

AI Code Review and the Software Factory 5:56
Building a 'software factory' requires more than just plumbing; it requires self-improvement loops that continuously refine the context and skills used by coding agents. Code review is positioned as a critical loop that feeds back into the factory to improve code quality before merging.
Customization via Lenses and Globs 22:07
The system uses customizable 'lenses' (review rules) that can be tuned to specific domains (e.g., audio DSP) and restricted to specific file paths using globs. This allows for highly targeted reviews, even in large mono-repos.
Local and CI Integration 23:50
Tessl Code Review can be run directly via the CLI (`Tessl code review give it the profile`) against local changes, enabling developers to catch defects before opening a PR, complementing its automated GitHub app integration.

Watch on YouTube Full article

Jul 23, 2026 · 19:18

Harness Engineering is not Enough: Why Software Factories Fail — Dex Horthy, HumanLayer

The video argues that current efforts in 'harness engineering' and increasing tokens are insufficient for building reliable AI software factories because they fail to address fundamental model training shortcomings. The core problem is maintaining codebase quality over time (maintainability), which current reward functions do not penalize. To move forward safely, the speaker advocates returning to rigorous human-led upfront planning: Product Review $\rightarrow$ System Architecture $\rightarrow$ Program Design (down to types and call graphs) $\rightarrow$ Vertical Slices.

Key takeaways

The Failure of 'Lights Off' Factories 12:10
Attempting to run a software factory with no human code review ('lights off') leads to failures, even for advanced agents. The issue is not scale or prompting, but a fundamental model training limitation.
Model Training Flaw (The Maintainability Gap) 17:12
Current coding models are primarily trained on passing tests and solving one-off problems. Their reward signal does not penalize poor program design or the erosion of codebase maintainability, meaning they get better at passing tests but worse at keeping large systems stable.
The Path Forward: Structured Planning
To move faster safely, engineers must re-emphasize upfront planning steps: Product Review (desired behavior/mockups), System Architecture (component contracts/data models), Program Design (types and call graphs), and Vertical Slices (implementation order).

Watch on YouTube Full article

Jul 7, 2026 · 58:11

Responsibly Abandoning Open Source Projects - Jason Turner - NDC Copenhagen 2026

This talk outlines best practices for developing and maintaining open-source projects to ensure they can be responsibly abandoned or handed off years later without becoming 'legacy' or 'abandoned.' The core focus is on achieving a state of 'completeness' by implementing rigorous automation across the entire development lifecycle—from static analysis and comprehensive testing (including path coverage, fuzzing, and mutation testing) to simplified build processes. Key recommendations include automating all quality gates within CI/CD pipelines and minimizing technical debt related to tooling complexity.

Key takeaways

Achieve 'Completed,' Not 'Abandoned' 20:30
When concluding work on a project, aim for the status of 'completed' rather than 'abandoned.' This requires proactive measures like maintaining clear documentation and ensuring continuous automation.
Automate All Quality Gates 29:55
Implement automated checks for every possible tool (static analysis, dynamic analysis, formatting) to ensure consistency and reduce friction for future maintainers. This should be fully integrated into the build process.
Prioritize Strong Typing 34:45
Adopting strongly typed systems (e.g., using type hints in Python or dedicated types like `Point` and `Color`) makes code less prone to order-of-operations errors, significantly improving robustness.
Minimize Build Setup Friction 32:10
A new contributor should be able to set up the development environment and run all tests/analysis in a minimal number of steps (ideally five lines or less).

Watch on YouTube Full article