How often do you debug via bisection? Do you know how? How far do you take it?

@zenspider I use git bisect about once per year.

@getajobmike really?? is that because it's mostly just your own codebase?

I have to bisect anywhere from 10-100 times a week.

@getajobmike alternatively, what's your usual debugging toolset/process look like?

@zenspider yeah, Sidekiq’s stable codebase doesn’t change much, most issues I can debug solely with my mental model.

@getajobmike man... if *only*

@zenspider Depends on what you mean - I pretty rarely reach for git bisection (except on one particular team/codebase - I think because it was a) needlessly complicated and b) important bugs were much later than when they were introduced).

Test case bisection I’ve only really used once in a codebase to find flaky tests - the rare codebase I’ve worked with that a) had a lot of tests but b) not enough discipline to find and fix the flaky tests.

But if you mean bisection via print statements? I do that shit all the time.

@zenspider @getajobmike how are you using bisection at all when half of the intermediate commits won’t build at all?

@kjtsanaktsidis @getajobmike you're making an assumption that doesn't hold