What happens when the Board Of Discourse begins to panic?
-
Second idiocy: He was repeatedly told that nobody wanted to hear about the weak programmer. Repeatedly. How often does he have to be told to stop banging on about something before he gets the message?
I don't think this was idiocy on his part. He's asked to assume responsibility while having someone "sabotage" the project through incompetence. Unless he's given a valid reason for why they don't want to hear about the weak programmer ("he's one of the investors' son, our funding depends on keeping him busy"), bringing him up every time is the right thing to do until the problem is addressed to his satisfaction.
-
Pfft. Doesn't even work.
-
You are "The guy who has a shitload of corpses in his basement, don't touch his Windows XP".
My Windows XP machine is in the basement. By the time you've seen it-- it's too late.
-
Yeah it doesn't return me or Dutroux.
-
The computer would need to understand this
If you can get a computer to understand how Belgium works, you’ve made one that can do more than most humans.
Pfft. Doesn't even work.
But at least you’ve found where [url=http://thedailywtf.com/articles/self-service]Joep[/url] has been hiding out since making Anna’s life difficult.
-
-
I'll call shenanigans on that "statistic". If all of the Top 20
Sub Commanders were ~30ish I really doubt the :uk: Sub Commanders were that far off.
-
I'll call shenanigans on that "statistic". If all of the Top 20
Sub Commanders were ~30ish I really doubt the :uk: Sub Commanders were that far off.Nitpick:
is the flag of the Federal Republic of Germany. You were looking for this one:
-
Aaaaaand @bb36e and @DCRoss get to share the coveted Siren award. Or is it half-Siren, since the OP didn't join in? Quarter Siren each?
Re: the article
Excellent read. Highly recommended despite the length.
I especially enjoyed this Milburn character, and insights into his salesman tactics. I'd like to think I'd stay as composed as the OP claims he was, but no, I'd probably crumble two minutes in.
Of course, it'd always be nice to see the same story from other POV-s. Could turn out the OP was the asshole all along.
-
WAY TO BE A FUCKING NAZI...NAZI!
ALSO FUCK DUCKSAUCE! DICKHOLES! Here's some normal text.
-
-
That's how I image all natural-German. 90% yelling, 10% normal-speak.
-
INDEED. WE ALL TALK LIKE THAT OVER here.
-
I KNEW IT! YOU SNEAKY FUCKS WOULD BE SNEAKY-ER IF YOU YELLED LESS! Also fuck discourse.
-
IT'S GREAT FOR MY GRANDMOTHER HOWEVER SINCE SHE IS HARD OF hearing.
-
WELL SHE SHOULD HAVE AVOIDED THE PARTY-RALLIES! EVERYONE KNOWS they are LOUD AND FUCK YOUR HEARING UP!
WHY ARE WE YELLING AGAIN!?!?
-
WE ARE YELLING? SOUNDS NORMAL TO me.
-
WELL SHIT. MUST BE USER
SYNdrome.
-
I was just pointing out that the awkwardness of typing on a mobile device is probably a moot point since they'd prefer their customers to use speech-to-text instead, which is easier to train.
That's the fallacy of speech-to-text. You don't train the software to recognize words. The software trains you to speak in a very specific way that it understands.
-
It's easier to train a user "Just talk to the bloody thing, you can figure that out, can't you?" than having to explain buttons, is what I meant :)
-
Woohoo!
-
I'll call shenanigans on that "statistic". If all of the Top 20
Sub Commanders were ~30ish I really doubt the :uk: Sub Commanders were that far off.
@Steve_The_Cynic didn’t say anything about whether the multiple British warship commanders who were in their early 20s, were “Top 20”. (Top 20 in what respect, anyway? Ships sunk? Enemy ships sunk? Pop music chart?)
-
-
8 posts were split to a new topic: Vaccines Are EVILZ!!!
-
4 of the top 20 on that list would have been early 20s around 1939. Based on that list, all 4 didn't get command earlier than 24 which I would say is pushing the definition of early 20s.
Looking up British sub-commanders was tougher. I've managed to find ONE commander that would have fallen into early 20s when he got to skipper a sub. Was there 1 21-year old skipper? Maybe? More than 4? I highly doubt it.
-
At the very least, he is leaving the impression that either he has a vendetta against the guy (and this repeated bringing-up of the issue is part of it) or that he doesn't listen when told to shut up about things.
Neither of these is a good thing to induce people to think about you.
Ergo, he's an idiot.
-
At the very least, he is leaving the impression that either he has a vendetta against the guy (and this repeated bringing-up of the issue is part of it) or that he doesn't listen when told to shut up about things.
If Nagesh-man was the only problem this project had, I wouldn't shut up about him either. I'd probably force the decision by saying "either you fire him or me".As it was, yes, he could drop that one :WTF: and still have more than enough to talk about to his bosses.
-
The board seems standard
US style: arrogant, aggressive, and blind to their own errors and ignorance, as if becoming a chairman automatically turns you into Oppenheimer.FTFY.
Don’t you parse my words! Don’t you dare do that! Don’t try to derail this conversation again!
One of many lines from this text which would result in me simply responding with 'whut?'. It's my go-to phrase when confronted with nonsense. It's also my most civilised phrase when confronted with this kind of nonsense.
I wonder how many seasons of situational comedy could be generated from a sassy back-talking dev who comes up with different variations on "You fucked up so you're trying to blame me."
I'm betting on two. The second season would be bad and get axed, but only because the best writer (who was half-jewish) left for family reasons and the producers never hired a replacement. They were more interested in their other project: Dogs Driving Cars, which ultimately failed a season later.
-
Source
No idea where this should link to...
-
I should elaborate a bit on this. When someone like the true-CEO asks you if you can guarantee something, if you can (Lawrence clearly could not, and he knew it) then you say, "Yes, of course." If you cannot guarantee it, you do not waffle on about this and that. You must simply say, "No." Sure, it sounds weak, but waffling on sounds even weaker. If he wants to know why you cannot guarantee it, he'll ask. If he doesn't ask why you can't guarantee it, you might ask him if he would like to know why, but I'm pretty sure that's a bad idea.
You should instead take away the message that he was looking for you to admit something negative about yourself. Perhaps because he has it in for you, but perhaps because he wants honesty from the people working for him.
But Lawrence waffled on about what amounts to a load of "this and that" rather than spitting out the answer. He continued to waffle in the face of someone shouty demanding a simple yes/no answer repeatedly. He's an idiot of the first order.
Had a similar thing happen in court recently (which is why I was absent for a time, preparation and all).
The prosecuting attorney was cross-examining me regarding the incident. After providing a detailed answer to her last question, she admonished me by saying: "next time, answer the question, don't give me a novel." I nodded. This set up the next exchange. She says: "My witness claims that you told her 'If you go to the police and file charges, we will all lose.' Is that true?" To which I replied: "Taken out of context, yes, absolutely."
She didn't seem pleased with my answer. But it didn't matter - long before that point, my accuser had already been proven a liar and exposed for attempting (and failing) to extort me via contradictory "evidence" she submitted, and the Judge ruled as such. Note: the worst thing a Judge can ever say to you is: you're not credible, as he did to her.
Perhaps I'll write up the story one day - after I'm done cleaning up the damage.
She didn't get the message (religion proven by science reference, less than a minute long):
https://youtu.be/_RcqKGCIRiU?t=15m39s
15:39 - 16:16
-
Note: the worst thing a Judge can ever say to you is: you're not credible, as he did to her.
"You won't be able to bamboozle the bankruptcy judge" comes close.I was left (after hearing this) to file a "Creditor's petition for bankruptcy" against the person this remark was directed towards. This is a feature of English bankruptcy law that I believe doesn't exist anywhere in American law, where a creditor (or a group of creditors) can file to have a debtor (a physical person) made bankrupt. It was a sorry tale, one that taught me far more than I ever wanted to know about English contract law.
But it also left me with another oddity: there is a similar petition available for cases where the debtor is a corporation. There is a minimum amount for the debt, but at the time (2005) that figure was just 750 pounds, around $1000, same as if the debtor is a physical person. If the largest company around provably owes you more than that and won't pay, you can petition to have it wound up. (In reality, the menace of such an act would suffice to make even the most stubborn company cough up the money.)
-
I haven't had to use that one myself but it's a loophole I have made other people aware of to get what they were owed.
-
I was left (after hearing this) to file a "Creditor's petition for bankruptcy"
-
OK, I didn't know that. Left-Pondish people keep talking as if it isn't a thing. TIL that it is.
-
But it also left me with another oddity: there is a similar petition available for cases where the debtor is a corporation. There is a minimum amount for the debt, but at the time (2005) that figure was just 750 pounds, around $1000, same as if the debtor is a physical person.
It makes sense to me for such a rule to not depend on the size of the debtor, as the rule is there to protect the creditor not the debtor.
-
@Steve_The_Cynic said:
But it also left me with another oddity: there is a similar petition available for cases where the debtor is a corporation. There is a minimum amount for the debt, but at the time (2005) that figure was just 750 pounds, around $1000, same as if the debtor is a physical person.
It makes sense to me for such a rule to not depend on the size of the debtor, as the rule is there to protect the creditor not the debtor.
I agree. It's just that the minimum size of the debt required is a bit smaller than I expected. You can reach £750 trivially in a small-claims track action, because all manner of expenses(1) get added to the debt by the courts, and they count as part of the £750.(1) Including silly stuff like mileage to get to the court, chargeable if the judge feels like it at 40 pence a mile (2004, normal Inland Revenue tariff). Granted, consumer-vs-business actions take place in the consumer's home court, but even then, it might be 10-15 miles or maybe more each way to the relevant county court, doubled (to get home afterwards), so there's a good ten quid added to the debt for each relevant hearing. Plus the court fees themselves, and ... So £750 for a bankrupting (or insolvency-inducing)(2) debt is not even hard to achieve.
(2) In English law, bankruptcy is for individuals, and insolvency is for corporations.
-
This was a case where we were sabotaged by the strict typing of Java.
(My apps were written in Clojure, but his app was written in Java. They
communicated by sending JSON objects to each other, via Redis.) Since we
were changing the data structure every 4 or 5 minutes, we were getting
endless cast errors. At some point Pranab tried to speed things up by
casting everything to Object, but that simply moved the errors from
compile time to run time. If we had been using Clojure, and simply
manipulating hashmaps nested inside of hashmaps, then 50% of the errors
would have vanishedSure, blame Java instead of blaming, say, "changing the data structure every 4 or 5 minutes" and having no real type safety or isolation.
-
Sure, blame Java instead of blaming, say, "changing the data structure every 4 or 5 minutes" and having no real type safety or isolation.
Yeah, honestly, with 2 separate apps, even if they were both just "manipulating hashmaps nested inside of hashmaps," you're going to be left with the runtime errors.
-
Especially with hashmaps within hashmaps.
As a rule of thumb, I find that turning compile-time errors into run-time errors is most of the time a bad idea, when it's not specifically done for the purpose of making them recoverable and introducing a good fallback mechanic.
-
-
It's
E_STACK_OVERFLOWall the way down!
List of World War II U-boat commanders - Wikipedia
