In his team, they have a full-size Justin Bieber cutout that gets placed facing the team member who broke the build

I've been part of projects in the past where people were paralyzed by fear of breaking the build - where they spent unjustifiable amounts of time developing code just to avoid Justin Bieber.

A better approach is to have the code control system automatically detect the build breakage and back out the change that caused it, send a polite notice to the person responsible for the change, and let work proceed. It's also helpful to pay some attention to what makes the build so fragile.

This. Shaming people isn't good management. I've actually heard that Spacex is a shiat place to work.

I once worked with a relatively useless woman who was also a rabid Feminist. She considered any criticism (no matter how valid or justified) to be "harassment".If a build was broken, she was responsible about 50% of the time (the rest of the team the other 50%).We originally had a policy that whoever broke the build had to wear a hat that said "I broke the build".

Anyway, we changed the policy so that whenever someone else broke the build, they were responsible for making "her" wear the hat the next time she broke the build.

Needless to say, the incidence of broken builds very quickly dropped by 50%.