Drowning in a C of Interviews
blog.bitquabit.com
Drowning in a C of Interviews
1–10 of 24 posts
Re: Drowning in a C of Interviews
#2This isn't a C-specific problem; of course people are going to be more relaxed in their comfort zone. If you asked me to write a Web server in Python, I'd be a lot more relaxed about it than if you asked me to do the same in Forth. There's a reason nothing changed when he dropped C (what goes unsaid: is he putting C in the job description?).
Joel's observation about pointers is dead-on, but I've personally beat that horse on HN in the past and will spare everyone a greatest hits anthology.
Re: Drowning in a C of Interviews
#3I really did like getting interviewed in C. :) But I was also confident using it.
It was appealing knowing that interviews were conducted in a language that wasn't really being used. Lots of companies claim they will hire smart people regardless of skills, but then you show up to interview and the guy across the table really expects you to know python and is flabbergasted that you bothered applying without it. I felt Fog Creek really demonstrated commitment to the principle by interviewing in a "useless" language. As someone with a bit of experience looking to make a change, it was a nice touch.
Re: Drowning in a C of Interviews
#4This blog post seems to have the feel of someone interpreting scripture. Only in this case, the author of the scripture is also the one he's presumably challenging with his interpretation. I assume Joel is ultimately responsible for the existing FC approach to interviewing... (?)
Re: Drowning in a C of Interviews
#5I really did like getting interviewed in C. :) But I was also confident using it. It was appealing knowing that interviews were conducted in a language that wasn't really being used. Lots of companies claim they will hire smart people regardless of skills, but then you show up to interview and the guy across the table really expects you to know python and is flabbergasted that you bothered applying without it. I felt…
You're pretty deluded if you think that C is a "useless" language.
Re: Drowning in a C of Interviews
#6I interviewed at Fog Creek recently (and I don't think it was with Ben, the post's author), and I actually didn't code in C. I answered my questions in Python, just because I'm more comfortable with it these days. So I don't know if this is a new thing they are trying out, or if internship interviews are different.
(I believe I'm allowed to say this about the interview. If Joel or someone at Fog Creek comes across this and takes issue, just let me know and I'll remove the post.)
Re: Drowning in a C of Interviews
#7I really did like getting interviewed in C. :) But I was also confident using it. It was appealing knowing that interviews were conducted in a language that wasn't really being used. Lots of companies claim they will hire smart people regardless of skills, but then you show up to interview and the guy across the table really expects you to know python and is flabbergasted that you bothered applying without it. I felt…
You're pretty deluded if you think that C is a "useless" language.
It more or less is at Fog Creek. I am not unfamiliar with the usage of C outside of Fog Creek.
Re: Drowning in a C of Interviews
#8Earlier quoted context omitted.
You're pretty deluded if you think that C is a "useless" language.
It more or less is at Fog Creek. I am not unfamiliar with the usage of C outside of Fog Creek.
They have their own compiler for a custom VBScript derivative. If there's no C anywhere in it, I'd be surprised, but I am operating without knowledge of its implementation or output.
Edit: So what did I do wrong here? I admitted that I'm shooting in the dark, admitted that I'd be surprised if my hypothesis was true, and had absolutely no knowledge of who the person I'm replying to is. It's certainly not on his profile.
I put forth an incorrect assertion, a couple comments corrected me and I was happy to learn this insight, but my comment is already -1 because I'm what, not contributing to the conversation? Or because I was wrong? Do you have to vote on everything?
It's really interesting to me that HN whines daily about the decline in comment quality, then turns around and grays this comment. Decline of HN, indeed, downvote everyone unless they're correct or a valued member of the community. After yesterday's observations I figured I'd give it one last go, but now I just hope this community dies the hypocritical death it deserves.
Re: Drowning in a C of Interviews
#9I interviewed at Fog Creek recently (and I don't think it was with Ben, the post's author), and I actually didn't code in C. I answered my questions in Python, just because I'm more comfortable with it these days. So I don't know if this is a new thing they are trying out, or if internship interviews are different. (I believe I'm allowed to say this about the interview. If Joel or someone at Fog Creek comes across th…
If you interviewed in Python for a dev position, then you interviewed with me or one other coworker who is also trying this experiment. The majority of Creekers still do their interviews in C, and are in fact passionate about it: http://thoughts.rockhymas.com/post/4580899270/in-which-i-def...
Re: Drowning in a C of Interviews
#10It's a bit hard for me to believe that there are programmers, who dont understand Pointers!
Though I am still in school, I feel everyone should understand how Memory works.
My assumption is that everyone should at least know about:
1. Pointers and their physical meaning
2. Difference between Process specific virtual memory and physical memory
3. Difference between Static, Stack and Heap Memory.
4. Also it is important to understand what happens when a disk access is required, and difference between Random reads and Sequential reads.
5. Bonus if you can understand, how swapfs is utilized and L2,L3 cache work.