News for hackers. Stuff that matters.
Re:The Imposter's Handbook by cmrdporcupine on Wednesday August 24, 2016 @10:20AM (#12352202)
Having a CS degree gets you through a Google-style interview -- where they will hammer you for hours on your ability to recall the skills you needed to pass your algorithms classes in university, and grade you almost solely on that.

And then you will start working there and almost never use those skills again, because you'll be using a vast library of datastructures and algorithms in the language of your choice, and the skill you will need the most is the ability to analyze why you might need one vs the other.

Unless you're on the team which is writing said libraries, which is rare.

Re:The Imposter's Handbook by nostrebored on Wednesday August 24, 2016 @11:32AM (#12352758)
Implementation is only a portion of what's important in an interview. The thing you will not get anywhere without is a knowledge of what algorithms exist and when to use them.
Re:The Imposter's Handbook by cmrdporcupine on Wednesday August 24, 2016 @11:43AM (#12352838)
You will not get through a Google style interview knowing what algorithms exist. You will be expected to implement them. On a whiteboard. Almost perfectly. Without access to a computer.
Re:The Imposter's Handbook by nostrebored on Wednesday August 24, 2016 @12:13PM (#12353072)
"Only a portion". And almost-perfectly is a big deal. You're not expected to write compiler-ready code, just to show that you understand what's happening under the hood. Which meshes up with practical expectations -- if you can't understand what potential bugs/space/time complexity you're introducing when leveraging a library, then you're a fundamentally worse coder than someone who can.
Re:The Imposter's Handbook by estefan on Wednesday August 24, 2016 @12:33PM (#12353234)
Except this is in fact bullshit since if you're ever working on some speed/memory critical code, that's the time to bother filling your brain with the different options available and picking the appropriate one. Carrying around arbitrary knowledge to show off is pointless.

Most code most programmers write won't ever run at sufficient scale or be sufficiently critical that CPU or memory bounds will matter, and using e.g. one sorting algorithm vs another will be largely irrelevant. It's recognising when you need to bother optimising that is the sign of a competent developer.

And asking someone to write actual (not pseudo) code on paper/whiteboards - as I've seen in interviews - is like assessing someone's driving ability by asking them to mime driving a car.

Re:The Imposter's Handbook by cmrdporcupine on Wednesday August 24, 2016 @08:42PM (#12356228)
I agree.

But it's worth pointing out that a Google style interview also includes some portion which is "system design" oriented which would touch more on that kind of thing.

But they're more interested in avoiding false positives, than false negatives. So the process is designed to weed out most people.