Live data from Hacker News

Continuous Integration Failure? Use USB Missiles

papercut.com

21–30 of 31 posts

Re: Continuous Integration Failure? Use USB Missiles

#21
post #4

Excellent stuff. I had a similar idea once, hooked it up to an irc channel and made a bot with commands to shoot people in the office by typing their name. Unfortunately I couldn't get the rocket launcher to be accurate as the same command sequence wouldn't always result in the launcher aiming at the same position.

You need a rocket launcher with servo-motors to get repeatable performance.

Re: Continuous Integration Failure? Use USB Missiles

#22

>It works on a deep psychological level to offer vast productivity improvements. some other extremely effective methods used in [another organization where people are treated like sh!t] the Russian Army: blocking access to the exit door, restroom and/or food/water, gang-chaining and/to the utility pipes, forcing to wear gas mask [and if weather is warm enough - rubberized fullbody chemical weapons protective suite] .…

I can't seem to find where, but I remember reading about this a few years ago...

Some company had connected their Continuous Integration server to the exit door. Breaking the build would lock the exit door until the build was fixed.

Near the end of the day, some programmer would announce his big commit, and the rest of the team would rush to exit the room :)

Re: Continuous Integration Failure? Use USB Missiles

#23
post #17

As someone working in this office I must warn others of the constant fear this little device instils in you. It's like working at aperture science, the emphasis on testing is maniacal.

The CEO of Aperture Science was torn up and thrown into a fire.

Well, the computerized remains of his assistant / girlfriend, anyway.

"When life gives you lemons, don't make lemonade... Get mad!"

Re: Continuous Integration Failure? Use USB Missiles

#24
Is that a generation or culture thing? Where I used to work, it was the one golden and unquestionable and holy rule: if you break the build, you have to buy a crate of beer for the team - so you get the "punishing" part and you get some team building too because we would drink that beer during office parties, other special occasions or just in the evening before going home or out or over a casual chat.. or during some Warcraft or DotA sessions and that team still sticks together even nowadays that the company is long gone and we are working in different jobs and countries. I really miss that place for its team spirit and the people there.

And I must say, I felt almost offended when in my new job when I found out they didn't have anything like this in place at all.

Re: Continuous Integration Failure? Use USB Missiles

#25
post #22

>It works on a deep psychological level to offer vast productivity improvements. some other extremely effective methods used in [another organization where people are treated like sh!t] the Russian Army: blocking access to the exit door, restroom and/or food/water, gang-chaining and/to the utility pipes, forcing to wear gas mask [and if weather is warm enough - rubberized fullbody chemical weapons protective suite] .…

I can't seem to find where, but I remember reading about this a few years ago... Some company had connected their Continuous Integration server to the exit door. Breaking the build would lock the exit door until the build was fixed. Near the end of the day, some programmer would announce his big commit, and the rest of the team would rush to exit the room :)

Why not prop the door open instead?

Re: Continuous Integration Failure? Use USB Missiles

#26
post #20

Earlier quoted context omitted.

I doubt anyone would be threatened enough by foam projectiles to try to circumvent it. Now, getting someone else attacked for no reason is a different story. That would be amusing.

It could be stopped by setting a piece of cardboard a few inches behind your head.

Or by rolling your desk chair over a few inches

Re: Continuous Integration Failure? Use USB Missiles

#27
post #4

Excellent stuff. I had a similar idea once, hooked it up to an irc channel and made a bot with commands to shoot people in the office by typing their name. Unfortunately I couldn't get the rocket launcher to be accurate as the same command sequence wouldn't always result in the launcher aiming at the same position.

What model of rocket launcher were you using?

I think it was a Dreamcheeky. Here's a video of it being controller by an iphone app I wrote: http://www.colorfulwolf.com/blog/2010/03/11/iphone-rocket-la...

Re: Continuous Integration Failure? Use USB Missiles

#28
Not a fan of the psychological torture here. Why is "breaking the build" such a major problem? If the tests don't pass, the commit should go into a "testing" branch. If the tests pass, merge testing into master. That way you can fix things asynchronously, rather than wear a dumb hat or get shot at by missiles.

Re: Continuous Integration Failure? Use USB Missiles

#29
post #18

Earlier quoted context omitted.

Which is why 'Russian Army' is synonymous with productivity and effectiveness.

Sounds like the beginning of Full Metal Jacket.

now that you mentioned it :

http://www.youtube.com/watch?v=BTgrQ7W-taQ&feature=relat...

Typically happens at night when most officers left

Re: Continuous Integration Failure? Use USB Missiles

#30
post #22

Earlier quoted context omitted.

I can't seem to find where, but I remember reading about this a few years ago... Some company had connected their Continuous Integration server to the exit door. Breaking the build would lock the exit door until the build was fixed. Near the end of the day, some programmer would announce his big commit, and the rest of the team would rush to exit the room :)

Why not prop the door open instead?

IIRC, this practice was put in place by the developers themselves (not by management), as some kind of "productivity joke". Propping the door open would defeat the purpose.

I'm seriously annoyed that I cannot seem to find the original story...

Post reply on HN