Reminds me how uncle bob warned us that some day when the software industry is regulated, git blame will send some sorry engineer to jail.
He's been a driving force in giving programmers in large organizations the vocabulary and ammunition to win arguments that lets them write proper software and not shitty software. If you find yourself writing Java in a bigco IT department and you want to introduce stuff like test driven development, code reviews, or whatever else is just proper engineering practices, reading/watching some Uncle Bob is probably going to help you convince your coworkers and bosses.
He has some rather controversial ideas (eg he believes that "flow"/"the zone" is bad and programmers should never be in it), but you don't need to agree with all of it to learn something useful.
Software development shouldn't be a one-person job, that way, accidents are never a one-person responsibility. And criminal code should be caught in its tracks, too.