81–90 of 152 posts
Earlier quoted context omitted.
Most full-time, permanent jobs have a 3 month probation period at the start of the contract where the employer can fire the new employee easily.
What's your source for "most"? Also, why would I leave my job where I'm not on probation for a new job where I am on probation?
Earlier quoted context omitted.
Most full-time, permanent jobs have a 3 month probation period at the start of the contract where the employer can fire the new employee easily.
What's your source for "most"? Also, why would I leave my job where I'm not on probation for a new job where I am on probation?
I don't really care for this style of interviewing. A technique that really works is to take a problem the company is currently facing, slim it down and present it to the candidate pre-interview. Then when he comes in you ask him to explain his solution, and the choices he made. It allows the candidate to be far more relaxed and puts him in a situation a lot more akin to the work that he will be doing for your compan…
Earlier quoted context omitted.
I'm not sure I agree, actually. There were definitely several questions here I couldn't answer, but I definitely feel as if I should be able to answer them if I were going to work exclusively on the front-end (I'm primarily a back-end developer and have been for most of my career). I don't see anything here that seems absurdly trivia-esque. The coding questions were easy but I think coupled with the JS and even jQuer…
I used to use these questions to interview candidate but found it to be really off putting and not terribly helpful. What’s more important than their answers to these questions is how they got there. Have they vertically centered an element so many times it seems second nature? Did they find it in an unsubstantiated StackOverflow post? Did they write a C program to lay it all out using spans? The bigger computer scie…
Usually I was using this list as a topic and of course I also don't know the answers of every question, but I pick the questions that are relevant to the company's tech stack.
Anyone else feel like there is a lot of esoteric information here? For instance: > Are there any problems with serving pages as application/xhtml+xml? I've never had to or considered serving pages as application/xhtml+xml, there's no reason for me to know the answer to this question and I've been working on the front end for ages. If I ever had reason to serve a page application/xhtml+xml I would thoroughly research…
I think VML's response is valid here, it's to check for experience and if you were engaged enough with the happenings of the web at the time.
Background (not a 100% accurate, I'm writing from my admittedly poor memory):
XHTML and later XHTML2.0 were being pushed a while ago (early 2000s) as the next HTML language (succeeding HTML 4). At some point the community split and people from Mozilla, Apple and Google (I think) formed WHATWG to pursue a different (and faster) direction which is where HTML5 was formed, then later adopted back by the W3C.
One of the issues at the time when people pushed for wide XHTML adoption was that most people served pages as text/html which was basically wrong.
Serving pages as application/xhtml+xml triggered the XML parser instead of the HTML parser which is the "proper" way to parse XHTML.
The problem some people ran into was that the XML parser is way less lenient than the HTML parser. You _have_ to close your tags, you _have_ to escape entities, and if you had a single mistake anywhere in your markup the browser would render an error page instead of working around it.
There were also issues with in-lining JavaScript and having to wrap it in a CDATA block to stop the XML parser from attempting to parse it.
This was a headache for sites with user generated content and people in general seemed to not like the idea of having to clean their markup for what some perceived as very little gain.
Anyway, long story short, HTML5 won, XHTML didn't.
Earlier quoted context omitted.
Without asking technical questions, how would an interviewer weed out the people who say the former but can't actually back it up? Because if the above is the entire hiring process, your junior developers aren't going to have to be concerned about their imposter syndromes, because they'll be working along side actual imposters.
A startup I worked for made the applicants do pair programming for two days. Needless to say, the people getting hired were very good. Of course, if you are in a big company this is too much time and work (Recently had 6 interviews at big corps, not a single line of code written for a junior position)
How is this even possible for people that already have a job? Are they supposed to take two days vacation or do it in the weekend?
Earlier quoted context omitted.
Employment probation. We fired a few people right off the bat within 3 months because they very clearly bullshitted us. One guy fucking used notepad to code. I'm not joking.
What exactly is wrong with using notepad to code? No syntax highlighting?
Earlier quoted context omitted.
Call and apply are core concepts to writing good javascript. I would not hire someone (at least for any sort of senior role) that could not tell you exactly how both of them work. Many of the other things on this page are certainly "trivia" that could be addressed by google when they come up, but not those.
How often do you use call and apply? I've been a JS developer for a long time, have written a lot of JS code, and rarely need to use call and apply. Unless you're writing all your code from scratch and not using any frameworks / util libs (which you should) you won't need them very often.
Earlier quoted context omitted.
How do you get an employee to leave a permanent position for your temporary position?
Most full-time, permanent jobs have a 3 month probation period at the start of the contract where the employer can fire the new employee easily.
There may be more to the story, but in the absence of other information, "fired for using Notepad to write code" strikes me as being more on the arbitrary and capricious end of the scale than the rational and justified end.
It's a lot like firing a carpenter for using a screwdriver instead of a power drill with a screwdriver bit.