The fact that you have a Xyloc RFID card on your person is rather telling. Much more so than the fact that there is a USB stick on a neck lanyard laying there on the floor next to the spilled coffee.
Nothing like leaving evidence around (evidence that only serves one purpose).
Hats off to you for bullshitting someone into paying you that - because forgetting older people who would tear you to shreds... there are younger workers out there with 7-10 years experience who would leave you in the dust as well.
Older folks make better money, tend to laugh when their 35 year old boss tries to intimidate them, and are wise to corporate dirty tricks that zip right over a youngsters head without so much as ruffling that thick hair.
Well time zones, I would agree with. But I currently work on an Agile product with team members scattered around the US (Eastern Central and Mountain) and it is working pretty well (for an Agile product). Of course, that is not a huge time differential. I used to work on a huge project with team in the eastern US and Hawaii... not agile... and that just sucked.
I think for smaller projects, on a team with good interpersonal dynamics... Agile can really deliver a decent product fast, in the absence of any real requirements.
But those are the keywords: no requirements, fast, small. I have seem agile projects go right down the toilet also. YMMV.
There is no silver bullet with Agile. Plus, the fact that Agile doesn't scale well at all would make it unsuitable for many IBM projects I should suspect.
That said, many Agile-like practices could really help in some situations.
Didn't get the job - the reason is because their evaluation criteria is heavily skewed on academic CS skills: sorting, data structures, stuff like that. It is a good system, but it tends to filter out guys like me who have been in industry for decades and cannot remember the details of merge sort. They readily admit this aspect - at least they did to me.
Also, the writing code into a shared Google Doc was a bit cumbersome to say the least. Even though my stuff turned out to compile and run (and get the right result... I cut and paste into a dev env afterwards to verify... which I thought to be incredible considering I cold typed it into the equivalent of MS Word) I didn't get the gig. C'est la vie.
Slashdot Mirror
than self driving cars.
Why a specific USB device? This can be used for any device. Also, you can white list devices. Read the code, or is that not old school enough for you?
The fact that you have a Xyloc RFID card on your person is rather telling. Much more so than the fact that there is a USB stick on a neck lanyard laying there on the floor next to the spilled coffee.
Nothing like leaving evidence around (evidence that only serves one purpose).
A usb stick on a neck lanyard is quite common. The stick came out when you tackled me. I wasn't running USBkill. Prove I am lying.
It is invoking the poweroff command (shutdown on Apple), not yanking the power. Read the code.
I would imagine that the consequences of the information on the computer being compromised outweighs the inconvenience of an accidental shutdown.
I assume that your technique requires that the computer be powered on.
Ferengi are simply fictional characters reflecting human nature.
The moment he or she drives someone away, fire them.
Not a great example of modern C++.
Ask an unemployed US autoworker how well that plan has worked for them.
Hats off to you for bullshitting someone into paying you that - because forgetting older people who would tear you to shreds... there are younger workers out there with 7-10 years experience who would leave you in the dust as well.
that natives were there first. But this seems lost on young recruiters.
Ah yes, a youngster railing about the injustice and hypocrisy of the working world.
He is aging nicely I see. In two years you will be complaining the the country is going to hell.
Older folks make better money, tend to laugh when their 35 year old boss tries to intimidate them, and are wise to corporate dirty tricks that zip right over a youngsters head without so much as ruffling that thick hair.
"Buzzword" is a buzzword.
Well time zones, I would agree with. But I currently work on an Agile product with team members scattered around the US (Eastern Central and Mountain) and it is working pretty well (for an Agile product). Of course, that is not a huge time differential. I used to work on a huge project with team in the eastern US and Hawaii... not agile... and that just sucked.
Ha. Haha. Hahahahahahahahaha.
Sorry (wipes eyes).
I think for smaller projects, on a team with good interpersonal dynamics... Agile can really deliver a decent product fast, in the absence of any real requirements.
But those are the keywords: no requirements, fast, small. I have seem agile projects go right down the toilet also. YMMV.
There is no silver bullet with Agile. Plus, the fact that Agile doesn't scale well at all would make it unsuitable for many IBM projects I should suspect.
That said, many Agile-like practices could really help in some situations.
Too late, buddy. Should have thought of that before you jetted into that test tube.
Most guys get into this problem by shooting into a vagina... which is much more fun for the few seconds that the male orgasm lasts.
Actually, what I typed is not in any way like your statement at all.
...the moment he fertilized her ovum. He is the biological father, he is half responsible for these children if they are born.
He cannot force her to give them up any more than he could force her to abort the fetus or give the child up for adoption.
At this point I ask, "Dude what the FUCK were you thinking?" Could have saved her eggs without fertilizing them.
Fill it with explosives, give it a destination.
Such cameras might not be a altogether horrible idea.
Didn't get the job - the reason is because their evaluation criteria is heavily skewed on academic CS skills: sorting, data structures, stuff like that. It is a good system, but it tends to filter out guys like me who have been in industry for decades and cannot remember the details of merge sort. They readily admit this aspect - at least they did to me.
Also, the writing code into a shared Google Doc was a bit cumbersome to say the least. Even though my stuff turned out to compile and run (and get the right result... I cut and paste into a dev env afterwards to verify... which I thought to be incredible considering I cold typed it into the equivalent of MS Word) I didn't get the gig. C'est la vie.