|
Perhaps the units are different. Expected CTC is in millions, whereas current CTC is in thousands.
|
|
|
|
|
Avijnata wrote: Expected CTC is in millions, whereas current CTC is in thousands. Still no reason for it to be shorter.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Current: 9999 thousands
Expected: 100 million
Am i missing something obvious?
|
|
|
|
|
Avijnata wrote: Current: 9999 thousands Expected: 100 million Am i missing something obvious?
Sure. I like 10000 million better.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Encrypted
profile name is nice
Born To Learn
|
|
|
|
|
Nigel Planer.
I'm guessing you can put no for that.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
|
|
guide me to get those NP
Born To Learn
|
|
|
|
|
The only definition I know is "nondeterministic polynomial time".
/ravi
|
|
|
|
|
I am
-NP
Never underestimate the creativity of the end-user.
|
|
|
|
|
LOL I love the replies here, but I assume the correct answer is 'Notice Period'
|
|
|
|
|
Born To Learn
|
|
|
|
|
Here's a thought, ask them.
Have enough self-assurance to admit you don't know something and are willing to show ignorance. Demonstrates maturity.
Also, it will get you noticed, and that's what you want in this process.
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
|
|
|
|
|
From my time in India, I think some companies wanted to know your "Native Place". You may be from Australia (i.e. Australian citizen?!), working in India. Or perhaps from one state in India (e.g. Gujarat) working in different "current location" (say, Punjab).
|
|
|
|
|
Exceptional?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The "Worst deploy story" discussion prompted this discussion.
We had a remote server go crazy. Usually we can log in remotely and at least do something with it. But not this time. It was going nuts.
Our I.T. guy drove the 15 miles to the remote location and found someone had placed a heavy tool tray on the servers keyboard holding down one or more keys which kept repeating.
Only managers were allowed in the remote location's computer room. As expected, no one confessed.
Any more "Dumb Things People Do" stories?
|
|
|
|
|
The I.T. guy should have started to walk out with the tool tray and see who yelled.
|
|
|
|
|
trantrum wrote: someone had placed a heavy tool tray on the servers keyboard
Dumb!?! Ingenious more like.
It's a fantastic hardware virus.
I'm sure it was written by nefarious hackers and it is very difficult for virus scanners to pick up on this sort of thing.
|
|
|
|
|
I used to provide some mainframe automation by replacing the operators' terminals with PCs running emulators and some special servers talking directly to the mainframe.
I would get called out in the middle of the night (24x7 operations - an airline) because they kept losing connectivity for a few minutes almost every night at a random time between 1am and 3am. I couldn't work out what was happening except the PCs would lose connection to the servers because the servers would reset themselves for no apparent reason. It was as if the power had been cut off from the UPS and restored a few minutes later. I thought, "Aha! Faulty UPSes?". They were checked and reported themselves fully operational with no problems and no outages for months! Weirdly, this didn't happen at weekends.
So the following night, a Tuesday, I sat where I could see the server. At around 1:30 the cleaners came in and started cleaning. After a few minutes one of them came over to the UPS, unplugged the server, plugged in a vacuum cleaner, used it few a few minutes and then unplugged it and plugged in the server once more! The bodies were never found...
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Forogar wrote: unplugged it and plugged in the server once more! The bodies were never found...
True LOL!
Great story.
People are dumb. I are a people.
|
|
|
|
|
That reminded me of a client (before the days of remoting) that would call to report that the software was 'hanging' and timing out on some database operations. This only happened sporadically but usually once or twice a day. The application was a running on a PC in a small office of a warehouse. The SQL Server was housed in another office across the parking lot and the connection was a point to point wireless bridge. The worked well until a truck pulled into the dock blocking the signal. The client never made the 'connection' and it took an onsite visit to figure out.
"Go forth into the source" - Neal Morse
|
|
|
|
|
In the late 90s, I had the pleasure of meeting a consultant who provided his Windows Administration skills to several clients.
A story he told me concerned a client who repeatedly called to say that the "server was slow and it took forever to print".
He'd talk them through going to the server room, getting to the console, logging on, checking Task Manager, etc.
At which point the server would suddenly start serving and printing again.
He got this call several times. Eventually he went to the client site, went to the server...
And found to his dismay that someone had changed the screen saver from "Blank" to "Pipes" with maximum colors and complexity.
He changed it back to Blank. Problem solved.
|
|
|
|
|
This adds an entire new meaning to the word "dumb"
|
|
|
|
|
A couple of years ago a dev server I was using went down.
I went to investigate, it was on a desk in a room with a number of other low priority servers, stuff for which there was no room in the secure server room.
A consultant from a company doing work on behalf of someone had been setup in there, when his laptop battery was getting low he pulled a plug to make space for his.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|