Back in '84 at UC Santa Cruz, we had to write an 8086 assembler and linker. I was on the linker group, and we decided to create the 8086 BAT-Linker.
Error messages were a short dialog along the lines of:
Holy $SOMETHING, Batman! $ERROR_CONDITION occurred! Right! Quick, Robin! To the BAT-Debugger! But Batman, we don't have a BAT-Debugger! Even so, Robin, fatal errors are no excuse for poor traffic safety. Gosh, Batman, you're right! I never thought of that!
With the ATL (AC-130/chemlaser described above)... If you get hit by the beam, you're pretty much dead. Current RoE prohibit using a laser to intentionally blind or maim someone. ATL is really intended for attacks on physical targets where explosive munitions are either too noisy/obvious, or they can cause too much collateral damage.
Consider a case where insurgents or rebellious forces have taken over an anthrax factory. You don't really want to drop a JDAM on top of it. Or if they've set up near a culturally significant mosque. For political reasons, you don't want to drop a JDAM on their equipment.
You need to keep the laser on target with a long enough dwell time for enough joules to do the designated damage. Doing this while you are moving and the the target may be moving is not easy. Especially since the airflow and turbulence around your AC-130 can affect the energy flux.
Remember, an interview is a two-way street. The company is interviewing you to see if they want you to work for them, and [in soviet russia] You are interviewing the company to see if you want to work for them.
COMPANY 1 and COMPANY2 fail the second half. It's a matter of common courtesy and professionalism to notify someone with an appointment of an emergency change in plans.
So you passed the punctuality test, but you also have to realize that you're not the most important thing going on at the time.
I'm sorry. I had an appointment. I'm on the books. Does it kill them to say "Something came up"? I can understand that a crisis/whatever has come up, and am willing to reschedule. To leave someone in the lobby cooling their heels is plain rude and unprofessional. If a conflict has come up, LET ME KNOW and reschedule. Or would you consider it OK for an applicant to just not show up to an interview?
If you've decided you have the time to interview someone, then that time should be reserved for the interviewee. Again, I can understand crises, but common courtesy would demand a "this may take some time, would you like to wait, or should we reschedule?" And incidentally, I don't recall the specifics, but it didn't really sound like a crisis, from what little I did hear of the interruption discussion.
A while back, I was laid off, and went with a recruiting firm.
Recruiting firms suck.
COMPANY 1: I show up on time, check in at the receptionist. After 1/2 hour of being ignored while waiting in the lobby (not taking a test or anything), I leave.
COMPANY 2: I show up on time. After 15 minutes waiting in the lobby, I call the recruiter. 10 minutes later the interviewer shows up. During the interview, someone walks into his cube. Interviewer proceeds to ignore me for 15 minutes while he talks with the guy.
COMPANY 3: I show up on time, and am met and greeted courteously by the interviewer. He explains the job, and I immediately apologize for wasting his time. It's a DB job, and I don't know DB. I had told the recruiter I don't know DB. Interviewer and I agree that this was a mistake, and I asked them to keep me in mind for anything I *was* qualified for.
I don't like being tested, but given the shit that recruiters do (to both companies and applicants) I can see how it's necessary.
This suggestion is going to be modded to oblivion, but...
Remember, any bill must be signed by the President to become law (modulo veto overrides et al.). Hold your nose and write to Bush. Ask him to veto this law should it come across his desk. Use his own language and prejudices in your favor. Use terms like "Unwarranted government intrusion into business", and "liberal Hollywood elite".
Disclaimer: In the last two elections I voted neither Democrat nor Recpublican.
Actually, this is simply the DOJ remaining consistent.
Yeah. Prof was Phil Levy. What's your real name? Email me at redfloyd at gmail dot com.
And how is cured salmon fillet not salmon? :-)
Back in '84 at UC Santa Cruz, we had to write an 8086 assembler and linker. I was on the linker group, and we decided to create the 8086 BAT-Linker.
Error messages were a short dialog along the lines of:
Holy $SOMETHING, Batman! $ERROR_CONDITION occurred!
Right! Quick, Robin! To the BAT-Debugger!
But Batman, we don't have a BAT-Debugger!
Even so, Robin, fatal errors are no excuse for poor traffic safety.
Gosh, Batman, you're right! I never thought of that!
Exactly. Analog degrades "gracefully", while digital is pretty much all or nothing.
No, it's just salmon. You put both lox and creamcheese on a bagel.
JFK, I think.
CR would be problems described in prose, with about five or sex questions
Well, that explains it. Teenage boys ALWAYS think about sex
All of our students are above average!
With the ATL (AC-130/chemlaser described above)... If you get hit by the beam, you're pretty much dead. Current RoE prohibit using a laser to intentionally blind or maim someone. ATL is really intended for attacks on physical targets where explosive munitions are either too noisy/obvious, or they can cause too much collateral damage.
Consider a case where insurgents or rebellious forces have taken over an anthrax factory. You don't really want to drop a JDAM on top of it. Or if they've set up near a culturally significant mosque. For political reasons, you don't want to drop a JDAM on their equipment.
Yes and no.
You need to keep the laser on target with a long enough dwell time for enough joules to do the designated damage. Doing this while you are moving and the the target may be moving is not easy. Especially since the airflow and turbulence around your AC-130 can affect the energy flux.
I want my Duke Nukem Forever!
I've filed a couple of bug reports against GPL'ed software on this, because GPL specifically says you don't need to agree to it to use the software.
NASA issued a press release stating that in Kansas, the mission would be known as MAVID: Mars Atmosphere and Volatile Intelligent Design.
(and along that meme, whomever made the port flag differing in case between SSH/SCP different deserves a sound thrashing
Don't forget the config file flag being different between SSH and SSHD (one's -f, the other's -F, and I can never remember which)
Remember, an interview is a two-way street. The company is interviewing you to see if they want you to work for them, and [in soviet russia] You are interviewing the company to see if you want to work for them.
COMPANY 1 and COMPANY2 fail the second half. It's a matter of common courtesy and professionalism to notify someone with an appointment of an emergency change in plans.
So you passed the punctuality test, but you also have to realize that you're not the most important thing going on at the time.
I'm sorry. I had an appointment. I'm on the books. Does it kill them to say "Something came up"? I can understand that a crisis/whatever has come up, and am willing to reschedule. To leave someone in the lobby cooling their heels is plain rude and unprofessional. If a conflict has come up, LET ME KNOW and reschedule. Or would you consider it OK for an applicant to just not show up to an interview?
If you've decided you have the time to interview someone, then that time should be reserved for the interviewee. Again, I can understand crises, but common courtesy would demand a "this may take some time, would you like to wait, or should we reschedule?" And incidentally, I don't recall the specifics, but it didn't really sound like a crisis, from what little I did hear of the interruption discussion.
I always wonder why the "psychic hotline" people don't just win the lotto this way.
I also am always tempted to call them up and when they ask, "what's your name and CC#", say "You tell me, you're the psychic!"
A while back, I was laid off, and went with a recruiting firm.
Recruiting firms suck.
COMPANY 1: I show up on time, check in at the receptionist. After 1/2 hour of being ignored while waiting in the lobby (not taking a test or anything), I leave.
COMPANY 2: I show up on time. After 15 minutes waiting in the lobby, I call the recruiter. 10 minutes later the interviewer shows up. During the interview, someone walks into his cube. Interviewer proceeds to ignore me for 15 minutes while he talks with the guy.
COMPANY 3: I show up on time, and am met and greeted courteously by the interviewer. He explains the job, and I immediately apologize for wasting his time. It's a DB job, and I don't know DB. I had told the recruiter I don't know DB. Interviewer and I agree that this was a mistake, and I asked them to keep me in mind for anything I *was* qualified for.
I don't like being tested, but given the shit that recruiters do (to both companies and applicants) I can see how it's necessary.
Are answers such as "I do not know $LANGUAGE. I have not listed that as part of my knowledge on my CV. I am, however willing to learn." acceptable?
When interviewing or being interviewed, I prefer an honest "I don't know" to bullshit.
Is that a projector in your pocket, or are you just happy to see me?
OK, so they'll either:
1. Have a chair thrown at them
2. Have their F***ING air supply cut off!
This suggestion is going to be modded to oblivion, but...
Remember, any bill must be signed by the President to become law (modulo veto overrides et al.). Hold your nose and write to Bush.
Ask him to veto this law should it come across his desk. Use his own language and prejudices in your favor. Use terms like "Unwarranted government intrusion into business", and "liberal Hollywood elite".
Disclaimer: In the last two elections I voted neither Democrat nor Recpublican.
Oh yeah. Forgot about that. I suspect, however, that that's not what the OP was talking about.
WTF is Lunix???? Doesn't exist, according to distrowatch.
<BENDER>
In fact, forget the development!
</BENDER>