top | item 45505347

(no title)

shepardrtc | 4 months ago

At my last job, whenever a commit wouldn't build, we would blast it into a slack channel with an alert that included the comment and the name of the developer.

discuss

order

NordSteve|4 months ago

At one job, we had a garish chicken hat that lived in your office if you were the last one to break the build.

This was in the days before automated CI, so a broken commit meant that someone wasn't running the required tests.

vlovich123|4 months ago

Ah yes. Public shaming. The “beatings will continue until morale improves” strategy of code development. Next time, you may want to suggest an evergreen strategy where commits are tested before they’re merged.

baq|4 months ago

‘Works on my local’

arealaccount|4 months ago

We used to have a git plugin that snaps a picture on every push, which accompanied the "alert". Was fun.