|
OriginalGriff wrote: One important thing to remember: you have to sell the company to them as well. If they are any good, they want somewhere that they fit into comfortably - so if you give the wrong impression of what the company is like, they won't stay long; and recruiting is expensive! You should treat an interview as a two way process - them selling themselves, you selling yourself.
Things get really ugly when the company leaders start to believe their own propaganda. This can go as far as a total loss of any grasp of reality and employees are considered to be incompetent or lazy.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Problem solving. Given a problem, how does the candidate approach the solution; decomposition of the problem into sub-problems, and method of (re)solving each sub-problem.
One more thing is "What is your favourite topic/subject", ... followed by what was the most interesting learning you had in the last 3/6 months in this topic; "Can you explain this learning to me".
|
|
|
|
|
Sit him down with QA, and tell him to solve the top 50 unanswered problems.
If he makes an excuse and runs like hell, he's the one you want!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
now thats the best one i've heard in a while
#region(start signature)
Life's like a nose, you've got to get out of it whats in it!
#endregion
|
|
|
|
|
won't do that but yeah idea is good to go through top unanswered question for asking technical question rather than go through the same repetitive list of interview questions for .net or c#.
Ravi Khoda
Humanity is the best religion and smile is the best medicine.
|
|
|
|
|
One of my techniques is to try and help the candidate relax - I will usually make an erudite witty remark and if they don't laugh they generally don't get through.
Understand that this is as much to protect their sanity as it is to ensure that I can work with them - as if they get the job they will need to put up with my erudite witticisms on a daily basis
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
We haven't discussed this yet...now is a good time.
|
|
|
|
|
P0mpey3 wrote: .now is a good time
Just heard that Stuart Broad has became the fifth bowler of England to take 300 Test wickets.
I actually really like him
|
|
|
|
|
I am a big fan of him, too. I particularly like his this[^] over.
I ain't got no signature.
|
|
|
|
|
At this rate, I wouldn't fancy having tickets for the 3rd day.
|
|
|
|
|
I think the Highlights show will have to show the whole thing...and then show it all again just to fill the allotted time slot.
|
|
|
|
|
Due to time constraints, the Australia team only played the highlights.
|
|
|
|
|
3rd day? It's practically done already!
veni bibi saltavi
|
|
|
|
|
Aus-60/10. Broad-8 Wicket
|
|
|
|
|
Dharmesh .S. Patil wrote: Broad-8 Wicket
Aahhh.. He took almost all of them, wish I could just be there watching him taking the wickets
|
|
|
|
|
Cue the Krikkit robots...
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 believe the entire Aussie Test Team hove just applied for asylum in the UK in order to avoid certain death...
|
|
|
|
|
Good one
|
|
|
|
|
England have already made enough runs so they should declare the inning, win the game by today end and go for a 4 day paid vacation.
.AK.
|
|
|
|
|
They should have declared when they were 100 ahead and put them in again. Finish the game of in one day.
|
|
|
|
|
Going from SQL Server to Oracle.
Say goodbye to good tooling.
Say goodbye to civilized (T-)SQL (I think the PL in PL/SQL means Oracle outsourced the language to some cheap Polish labor... (no offence to Polish people)).
Say hello to steep learning curve.
All in all I just miss SQL Server.
Any "surviving Oracle for SQL Server devs" tips or guides?
|
|
|
|
|
You might ask the oracle...
|
|
|
|
|
They should've called it Miracle instead.
It's a Miracle anyone can get work done with this crap
I'm sure it'll get better as I figure this out...
|
|
|
|
|
Sander Rossel wrote: Any "surviving Oracle for SQL Server devs" tips or guides?
Tips and guides[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|