Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

We used to 'rain-bomb' each others terminals:

$ rain | wall

This was always really fun with the newcomers to the ops centers ..



sort by: page size:

So you renamed "controllers" to "operations".

Oh, I see. We have groups named "ops@" or "infra@" sometimes.

This is actually pretty standard ops methodology. You designate an "intake" person, and then the rest of the group works productively while only one person gets harrangued with interrupts. Its very effective.

Hello fellow Operator.

Ooh, I love this style of operator overload. Really clever.

Ops guys (almost entirely replaced by containerization).

(I kid, I kid)


What's the mood like? Are people excited to plug in and kill the baddies? Or is it just another day in the office yada yada Mondays are the worst? Do you prefer operators with previous gaming experience? Were there ever any operators that refused mission orders? how hard would it be for someone(higher ranking) to override an operators mission?

Probably around the same time ops were deemed useless :)

[1] https://news.ycombinator.com/item?id=13644789


But also for the ops, as it means securing one place instead of two.

That's just standard techbro ops 101.

Wow had no idea most of these operators existed. Thanks for sharing (and to the original post too, I didn't know a couple of those e.g. before:)

operators.

You're in ops? I could have sworn I've seen your name all over raven-js.

I bet it's awesome being the ops directory -- sounds like so much fun!

"operator operator fuck fuck fuck" usually works.

This is really simple, people. s/ops guys/ops team/g.

Done.


Sometimes the reason is that operations is used to it.

You just described a CISC op.

Cool idea! I like the overloaded operators.
next

Legal | privacy