231–240 of 309 posts
Earlier quoted context omitted.
I believe that's the IP address of Google Public DNS, not Google.com per se.
I beleive the exact question was: "show me an IP being used by microsoft or google" Are you really asserting that a google owned, and google operated service is not using the IP with which I access it?
Easy question
Earlier quoted context omitted.
It's an effective strategy from the employer's side, but what about the applicant who is asked to spend hours on some test for every job he/she applies for? Are you paying these applicants for the time they spend jumping through these hoops? And if your "technical grilling" fails to identify strong candidates, you're obviously asking the wrong questions or, at the very least, not asking the right ones.
As a candidate, I'd much rather they ask; I find that companies that don't ask for code are almost by definition unlikely to ask the right questions. If you must screen candidates for skillset, the less you have to rely on a proxy for that skillset the better off you are. As an employer, I find code samples irreplaceable, and I'm comfortable screening out candidates who decline to take the challenge out of principle…
Earlier quoted context omitted.
Not sure why you're getting downvoted, but debugging a "crack me" app while running as root is probably a bad idea. Even if this is inside a VM, it might give the wrong message to someone wanting to try this for themselves.
You could also attack the VM: http://www.cvedetails.com/vulnerability-list/vendor_id-93/pr...
Earlier quoted context omitted.
I've found that your job post determines the types of candidates you get. If you describe a really hard programming job, people self select out. If you describe an easy one, everyone applies. iOS developer? Floodgate. Crypto expert? Trickle.
Same experience here. We have an offering for normal java development with high performance aspects - tons of applications. Our monitoring/devops position? Few and far between.
Earlier quoted context omitted.
>Let the person know that (a) the computer is in working condition (i.e. no drivers are missing) (b) the network works (i.e cables are good, switch is good, DHCP is enabled, etc.) So you lie to them? I don't understand what the point of this test is. My first inclination is to open up a term and ping google but I would be pretty annoyed that your "first-wave" test involved actively lying to a candidate.
Every day, I have QA, tech support, my boss, and other developers tell me something that is not actually true, or simply omits any of the relevant information necessary to fix the problem. This is something you live with on a daily basis in a technical job involving complex systems that not everyone understands the entirety of. If you can't solve a problem with only some information, and some of it incorrect, then ho…
https://ericjang.quora.com/Reverse-Engineering-Apps-a-Step-b...
PS- You should buy ST, it is one of the best code editors out there in the market.
Earlier quoted context omitted.
Yeah, but B5Geek's is a pretty entry-level thing. I've encountered whiteboard tests where you have to recreate an algorithm that someone spent their PhD thesis creating. It seems like a good way to find "geniuses", but it just isn't practical. In a lot of ways, it's a matter of identity crisis for software developers. We're all, industry included, not quite sure whether we're mechanics, carpenters, architects or scie…
I've taken a whiteboard test that asked me to come up with an algorithm that was difficult for me. I got the job even though my solution was horribly inefficient (and I knew it), and the interviewer later told me that the point wasn't to see what algorithm I knew - it was to see if I acted like an ass when I didn't know stuff.
Surely there's more efficient ways of evaluating that.
This is Intro to Systems homework at UChicago (the course is heavily based on CMU's equivalent.) You're given a personalized binary that asks for a series of passwords to complete each level. If you get a password wrong, it phones home to a server run by the professor and decrements your grade. The point is to teach you to reason about assembly using GDB. You can pretty trivially set a breakpoint at the phoning-home…
How did it identify you as a student? Couldn't you alter the routine to bomb someone else's grade?
Earlier quoted context omitted.
True. Testing for sysadmins is easier: you're after a way of thinking . So a competence test ("can you do what you claimed?") with a freeform "keep notes on your thinking along the way" is quite informative. You still need to interview, of course. I confess I don't know how I'd apply this to developers. They pass fizzbuzz, OK - what do you do next?
> I confess I don't know how I'd apply this to developers. They pass fizzbuzz, OK - what do you do next? I know what I would do, just have a 10 minute conversation with them about technology. I can easily figure out just where a person is in regards to their development as a programmer just by listening to them talk about what they're paying attention to in the tech landscape. If they don't blink when I mention Hacke…