 Bisection (software engineering)

One of the Holiest age old debugging techniques!

Git has some helpers to help you achieve bisection Nirvana: stackoverflow.com/questions/4713088/how-to-use-git-bisect/22592593#22592593

Obviously not restricted to software engineering alone, and used in all areas of engineering, e.g. Video "Air-tight vs. Vacuum-tight by AlphaPhoenix (2020)" uses it in vacuum engineering.

The cool thing about bisection is that it is a brainless process: unlike when using a debugger, you don't have to understand anything about the system, and it incredibly narrows down the problem cause for you. Not having to think is great!

Bisection in software engineering typically refers to a debugging technique used to identify the source of a problem in code by systematically narrowing down the range of possibilities. The basic idea is to perform a "binary search" through the versions of the codebase to determine which specific change or commit introduced a bug or issue. ### How Bisection Works 1. **Identify the Range**: The developer begins with a known working version of the code and a version where the bug is present.