5 ms·
My kick-out questions: "Could you write out what an HTTP request and response looks like on the board?" I'm really surprised at how many people can't do this.
by djsumdog 10y ago
My kick-out questions:
"Could you write out what an HTTP request and response looks like on the board?"
I'm really surprised at how many people can't do this. If you've spent five years developing web, surely you've had to look at raw requests, either debugging using netcat or with wireshark or just looking at the information in the Chrome/Firefox debugger?
"What's the difference between a GET and a POST request?"
"What is the difference between a statically typed and a dynamically typed language?"
I had one candidate try to tell me Java was dynamically typed and Scala was statically typed. It was for a Scala position. They also said "statistically typed" instead of statically, even after I corrected them.
-_-
- GFischer 10y agoI believe 90% of my coworkers and former coworkers would be unable to answer the HTTP response question. And 95% haven't used netcat or wireshark. I wouldn't have either, if it wasn't for some particular work related to messaging. They're able to develop reasonable line of business websites in spite of that. I would be extremely worried if they were unable to answer about the difference between GET or POST, or the difference between statically and dynamically typed languages, so I agree with those.
- empath75 10y agoI basically lived in Wire shark for a couple of years working for a voip company and still use stuff like curl all the time and I don't think I could walk through an http request of the top of my head.
- figgis 10y agoBut could you describe the general structure? Yeah expecting many people to be able write out a complete http request from memory without a reference to look at. But the general structure of a http request is something so basic to web development that asking what the structure of a http request looks like isn't an unreasonable expectation. Request line (method, uri), header(s), empty, body...
- seanp2k2 10y agoGET / HTTP/1.1\r\n and some kind of sensible response is not too much to expect someone to know. HTTP is super easy and I see the HTTP transaction test as "did you ever get curious as to how exactly a core part of the current Internet actually works". I'm sure that there are app developers out there who can spin crud stuff all day and have no idea about this, just as there are curious people who couldn't stand up todomvc to save their life, but in general, all of the most talented people I've worked with knew their stuff front to back, and had at least a few areas of expertise. CGI is also cool to learn about the workings of, since it almost seems too simple.
- aninhumer 10y ago> I see the HTTP transaction test as "did you ever get curious as to how exactly a core part of the current Internet actually works". Sure I did. Then I forgot most of the details because they didn't matter, and I knew I could look them up quickly if I ever needed to write a HTTP client/server for some reason.
- dekhn 10y agoif you answer "GET / HTTP/1.1\r\n" I'm going to ask you if you left anything out. Because you did: after that you have to provide a Host: <hostname>.
- ninkendo 10y agoYou would've gotten it wrong though! You need two newlines to finis the request, plus the HTTP 1.1 standard requires clients to send a Host: header for all requests. Not saying every interviewer would care about that in an early screening process.
- jwatte 10y agoThere is some truth to the saying that some people don't have ten years experience, they have two years of experience five times in a row. Learning to use wireshark or tcpdump is a power tool that does show whether you got more experience in understanding the lower levels, or stayed at requirements-and-tests. (Not necessarily bad, but a good "fork" to jump off from)
- krzyk 10y agoWhy it is important to know the difference between statically and dynamically typed languages? If one writes in only one of those (or one set) it is not important to him/her and doesn't specifically make him/her a worse programmer in that particular language.
- steego 10y agoKnowing a cursory difference between a statically and dynamically typed language in this day in age is not an unreasonable requirement for many developer positions, especially web development where you're often using a mix of languages. As always, this sort of question is a test of competence by proxy and there are usually outliers, but statistically speaking, I think you'll find a very high correlation between inept programmers and people who don't know the difference.
- djsumdog 10y agoGeneral domain knowledge. We do Scala and a little bit of Python here and there. You should know the difference to show you're well rounded. Senior devs sound have some experience in both types. I have a follow up question, "What are the advantages of a dynamically typed language over a statically typed one?" This one kinda exposes the "Java-zellot" side of programming. If you love Scala and you're applying for Scala position, you don't often think like this. Being able to think critically about the things that are harder in Scala, that would be easier in a language without strict type checking, is a another good way to gauge if people can think critically.
- empath75 10y agoIf they didn't know it, I'd want to dig down into whether the understand the specifics of their particular language at least. I actually just sat down in a meeting with a dozen programmers, some of them with decades of experience, and half of them didn't know what functional programming was.
- krzyk 10y agoAnd the half that didn't know where much worse programmers than those that knew? Your example shows that not every programmer has to know that.
- mst 10y agoThe number of web devs I've encountered who regard my ability to talk HTTP over telnet as black magic makes me sad.
- lazaroclapp 10y agoIn all fairness, if you can talk normal HTTP 1.1 over telnet with some service, someone configured TLS wrong ;) And if you can talk HTTPS over telnet unassisted... well, I am truly impressed.
- micaksica 10y agoThere's always openssl s_client
- seanp2k2 10y agoYep, and when devs watch me key in the s_client pipe to OpenSSL to dump the cert info it's like I've become Neo and entered bullet time. I guess they don't need to know this stuff, but trying to do things like editing a hosts file in OSX, flushing dns, opening an incognito tab, looking at the SSL cert through the GUI, manually comparing it to one in an editor....vs a pretty short one-liner with curl or OpenSSL and a diff....I guess I'm either biased or lazy. I also almost never get asked WTF I just did, just a "wow, thanks" at most. A previous employer had a sysadmin wiki. We call it Devops now, but I really liked working with the plain-text files of Dokuwiki there. Confluence is good for some things, but as a notebook of shell snippets and when to use them, it's not great.
- micaksica 10y ago> I also almost never get asked WTF I just did, just a "wow, thanks" at most. Asking "wtf did you just do" is responsible for probably 1/5 to 1/4 of the professional knowledge I have today. It's sad that many people ignore that people will often teach you their little tricks if you ask.
- recursive 10y ago
- rimantas 10y agoI'd be able to write HTTP request by hand, I've done that quite often, however I would not expect that to be a common skill. Looking at something, even often does not in any capacity mean that you would be able to reproduce that from memory.
- TheOtherHobbes 10y agoExactly. These are memory tests, not ability tests. Beyond a very basic level, memory tests are too random to be useful. I once aced a geography exam because I happened to read up on the economics of Nigeria just before I took it. By sheer luck, there was a question about Nigeria in the paper. If I'd read about Zimbabwe instead I'd have been screwed. Neither possibility provided much insight into my competence as a geographer. Even if a job spec needs specific knowledge of key facts, you can't generalise from pass/fail memory questions to broad spectrum competence, or lack of it. If a candidate has no idea what an HTML request is, that's one thing. If they know damn well what a request is but can't list all the elements in a stressful interview while you're staring at them, - because in fact they spent the last year working on database code, and the API stuff was the year before that - that's something else entirely.
- throwawayIndian 10y ago> "Could you write out what an HTTP request and response looks like on the board?" Why should anyone remember what an http request or response should look like? Statically typed vs. dynamically typed language? Fuck. Are these entry-level positions or for someone with 10 years work-ex? A simple search on Google can tell anyone the answer of these questions, why do you expect people to carry an imprint of it in their memory? If the problem they'll work on mandates knowing these things it'd be pretty easy to solve with just one search. It is exactly questions like these that are worth kicking the host organization back in the butt. Either your interviewing process is hilariously stupid or you're just spiking it up to boost the ego here.
- whoops1122 10y agoI would not want to work for or with him, if he asked me that in an interview, I'd walk out.... if he think thats what good computer scientist should know...
- mikeash 10y agoStatic versus dynamic typing is so fundamental that I don't see how a programmer could be remotely competent without having been exposed to those concepts enough to have internalized them. It would be like an accountant not knowing what the number 4 is. Yes, you can look it up, but if you need to then how did you ever get this far?
- zzzcpan 10y agoIt is also a ridiculously dogmatic question. Many people believe into a fallacy that static typing makes safer programs, for example, and expect that somewhere in the answer.
- brianwawok 10y agoCould you explain how static typing makes less safe programs?
- 10y ago
- gehel 10y agoScala is statically typed.