311–320 of 441 posts
Earlier quoted context omitted.
That's probably a cyber crime in most US states. Edit: You guys have no sense of humor.
try /s at the end of "offending" sentence, most people will look at it more kindly.
Earlier quoted context omitted.
But why it even happened? Typically you run Flume over docjoins in your project’s quota. If you screw up, all that should happen is that your Flume job is out of quota.
This was in the Borg days, pre-Flume. As I remember, we had at least one Borg cluster to ourselves for indexing. Our quota was a cluster. We cared because indexing latency is important. Engineers get paged and woken up in the middle of the night when indexing latency gets high. Doubling CPU usage meant doubling indexing latency. The pre-Percolator indexing system ran roughly 1,000 threads per box on roughly 1,000 War…
Who. Who. Who. Who. Who. However. However. However. However. However. Why. Why. Why. Why. Why.
Took me right back one of many detentions I served at school, when Mr B Swales set us the challenge of finding a grammatically correct English sentence with five ands in a row. The answer was as follows: The landlord of the "Dog and Partridge" pub commissioned a signwriter to letter a new board outside. On looking at the work, the landlord declared that he liked the colour but would prefer more spacing between Dog an…
"Far, får får får?"
"Nej, får får inte får, får får lamm."
English would be:
"Father, does sheep get sheep?"
"No, sheep does not get sheep, sheep gets lambs."
No, google translate does not make it unscathed through that sentence :-)
Earlier quoted context omitted.
What a great story nevertheless.
It helped me empathize with young engineers dealing with their first high responsibility bug. About 4 years ago, I was managing a guy right out of school who pushed a minor bug that broke real-time risk calculations for a major multinational financial institution in the middle of the European trading day, prior to the NYC open, and people were yelling over email that they were trading blind. Someone had committed an…
Earlier quoted context omitted.
What a great story nevertheless.
It helped me empathize with young engineers dealing with their first high responsibility bug. About 4 years ago, I was managing a guy right out of school who pushed a minor bug that broke real-time risk calculations for a major multinational financial institution in the middle of the European trading day, prior to the NYC open, and people were yelling over email that they were trading blind. Someone had committed an…
Edit: if you are managing someone who is new in a job, it's your job to make sure they don't push bugs to break important stuff in the first place.
Earlier quoted context omitted.
It's easy enough to use a single "and" in a sentence, but "and and" and "and and and" and so on are more difficult
Clearly you've never taught intro boolean logic. Try saying "a Nand and an And" in a way that your students can understand you.
Earlier quoted context omitted.
I'm sure you're great. Nothing against you, but please don't do that. Just write what you mean if you can't handle some people misinterpreting a sarcastic remark. Let's think about this for a second. What's the point of sarcasm? If you have to tell people you're being sarcastic, are you still being sarcastic? Not sure what territory, "/s" blunders into, but I'm confident it's not sarcasm. It's something else that see…
To be fair, when vocalizing sarcasm, it is often marked by a particular tone. That tone is not easily conveyed online.
Earlier quoted context omitted.
What does it mean that you were right to feel embarrassed? You were wrong to make the mistake, sure, but that happens. That’s what a mistake is. It’s not clear to me what shame helps in this instance. If somebody has a pattern of not meeting a quality bar with their code that’s one thing, but otherwise cutting people up for mistakes really seems like bad culture. Aren’t you supposed to practice blameless postmortems…
My recollection from my time there, as well as one of the biggest cultural differences noticeable between my and my workplaces since, is that big chunks of the company really do believe in the blameless postmortem ideal. But culture isn't a magic tool that completely neutralizes assholes, and there are assholes in _every_ organization of sufficient size, like the "[name redacted]" character in the previous post