I'm very surprised you've never gone hunting for bugs in your git history.

"Hey something went wrong with X service"

Find commit like "add y to x service'

It's a time saver to me. Plus if the bug is extra tricky, you can ~easily~ revert or pick it out.

I did try when I was a junior. I learned this relies on good commit messages, and the information can be lost during squash. Honestly if I’m playing the role of bug detective I’ve become much faster using other techniques.

"I've found history is useless because people don't maintain good history, so don't bother with maintaining a good history"

Pick something that works != don't bother. But nice attempt at misrepresenting my argument!