When learning how to git bisect, you're learning two things: 1. the specifics of how to use git (*) to carry out a task 2. the conceptual underpinnings of the

When learning how to git bisect, you're learning two things: 1. the specifics of how to use git (*) to carry out a task 2. the conceptual underpinnings of the task, which would exist whether you use git or perforce or bitwarden or any future RCS. Being overly focused on either #1 or #2 is a mistake. It's not good understanding the task if you don't know how to use the tools you have right now to carry it out (or what available tools are appropriate). It's not good knowing how to run the tools if you don't understand what you're actually doing. The two go hand-in-hand. (*) not exactly the product of a mega-corp