Live data from Hacker News

Continuous Integration Failure? Use USB Missiles

papercut.com

1–10 of 31 posts

Re: Continuous Integration Failure? Use USB Missiles

#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.

Re: Continuous Integration Failure? Use USB Missiles

#5
>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] ... until the task is completed/corrected,

and the best of the best methods is to having [only] your teammates [who have no connection to the error] being forced into the above described conditions until _you_ correct _your_ own error. After it happens once, your teammates would make sure that you wouldn't repeat the error ever ...

Re: Continuous Integration Failure? Use USB Missiles

#6
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.

Sounds like if range is limited you'd need an array of multiple launchers, strategically distributed around the office to provide the most efficient coverage.

Re: Continuous Integration Failure? Use USB Missiles

#7
post #3

What is to stop developers from logging in remotely to commit changes, knowing that any attack will be directed at an empty chair?

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.

Re: Continuous Integration Failure? Use USB Missiles

#8
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?

Re: Continuous Integration Failure? Use USB Missiles

#9
post #6
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.

Sounds like if range is limited you'd need an array of multiple launchers, strategically distributed around the office to provide the most efficient coverage.

That would be especially awesome if multiple launchers engaged in the attack, resulting in a multi-directional barrage.

Re: Continuous Integration Failure? Use USB Missiles

#10
For simple things like build errors a local git hook was good enough to completely rid the project of those problems. For the Arora project I believe there were around 5 commits in the entire lifetime of the project that didn't build on one system and those were all cases were it built on the developers OS, but failed on a different OS. But man would it have been cool to have a USB missiles just sitting there waiting for the day they could launch.
Post reply on HN