|
|
Hire one.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Member 13193611 wrote: FUD crpyter
Looks like you are doing pretty well yourself.
|
|
|
|
|
Go forth and multiply - but not in those words.
You want to build malicious software - we don't do that. We do not condone, support, or assist in the production of malicious code in any way, form, or manner. This is a professional site for professional developers.
If you want to know how to create such things, you need to visit a hacking site: but be sure to disable all firewalls and antivirus products first or they won't trust you enough to tell you.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
OriginalGriff wrote: visit a hacking site: but be sure to disable all firewalls and antivirus products first
Isn't destroying the OP's computer a little harsh?
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I'm hoping they get his bank account at the same time! 
It's got to be worth a try.
Perhaps then he'll understand what idiots like him do to other people.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
What goes around comes around.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
|
That must have reminded the lion of the 2008's housing bubble burst. An appropriate reaction to that would be to become scared and flinch. Bonus points for running away. 
|
|
|
|
|
Hardly "terrified", more like startled.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Gotta love Jason Statham
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
This scene from Spy[^] is my favorite Jason Statham moment
Sorry for the bad quality... It's really just him talking anyway 
|
|
|
|
|
He is too violent: I cannot love him.
«When I consider my brief span of life, swallowed up in an eternity before and after, the little space I fill, and even can see, engulfed in the infinite immensity of spaces of which I am ignorant, and which know me not, I am frightened, and am astonished at being here rather than there; for there is no reason why here rather than there, now rather than then.» Blaise Pascal
|
|
|
|
|
I've spent hours, spread over days, on some #$&#$!*@!^#!* issue with Selenium and Protractor.
I had a test that sometimes worked fine (mostly the first two or three times) and most of the times didn't.
Searching, rewriting, waiting, logging, nothing seemed to help... I already found the server looped infinitely trying to get an element on my page.
And just now, I noticed the server always started looping at the same spot (which was pretty hard to see and remember sometimes it didn't loop at all and everything just worked).
So I fetch an element, click a button which removes the element from the DOM and then wait for the element to be removed from the DOM.
I guess sometimes the element removing would be a bit slower and the waiting occurred before the removal (it's all JavaScript multithreading/callbacks/promises, yuk...).
However, when the element would be gone before the waiting commenced the waiting would try to fetch the element to get it's status, couldn't find it, tried to find it again, couldn't find it, tried to find it again...
Fixed by just waiting a second.
So glad I've FINALLY found that issue!
Time to celebrate
|
|
|
|
|
With a glass of DOM perignon, no doubt.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Hold still Mark. We're going to have to hurt you now. 
Software Zen: delete this;
|
|
|
|
|
DOM == Destruction of Sanity
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Brisingr Aerowing wrote: DOM == Destruction of Sanity
Shouldn't that be "Definition of Madness"?
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Coincidentally, "Dom" is also the Dutch word for "Dumb"
|
|
|
|
|
So your "wait to see if the element is removed" would loop forever because it couldn't find the element if the element was already removed?
That is just too weird.
But congrats on finding the problem!
Marc
Latest Article - Merkle Trees
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: So your "wait to see if the element is removed" would loop forever because it couldn't find the element if the element was already removed?
Exactly.
Marc Clifton wrote: That is just too weird.
That's why it took me so long to find
Marc Clifton wrote: But congrats on finding the problem!
Thanks!
|
|
|
|
|
Sander Rossel wrote: Fixed by just waiting a second.
Do I understand this right -- you "fixed" the bug by waiting a second instead of polling the element's status?
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Yeah, because polling the element's status wasn't going to work.
Mind you, this is third-party software behavior.
If it were my own I'd fix the infinite loop instead.
Anyway, if this task takes longer than a second that's probably a bug too.
|
|
|
|
|
Sander Rossel wrote: Anyway, if this task takes longer than a second that's probably a bug too.
Or its running on someone else's machine
Poorly written third party software is the worst. Glad you found a way around them.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Had similar problem reading paper tape input where the next read executed before the last read's physical movement had ceased. Wait of 1/10th second fixed it. In 1965 I think.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
