People suck at technical interviews (2014)

Re:People suck at technical interviews (2014) by golergka on Friday June 10, 2016 @03:04PM (#11879055)

> "never mind 5 years of claimed SQL experience at a big company" - you can easily have that without touching JOIN.

Most of my experience with SQL comes from being a game designer with access to analytics database - so, not exactly a lot.

But how the hell would you not touch join even a single time while working with SQL for 5 years?!

[ Parent | on HN ]

Re:People suck at technical interviews (2014) by bobwaycott on Friday June 10, 2016 @03:20PM (#11879184)

Two ways I can think of off the top of my head:

1. Total reliance on ORMs, and never actually touching SQL (or not in 5 years since you started using ORMs)

2. Not building complex relational schemas with related items that you use SQL to pull in results of combined data that follows those relationships.

I'd wager #1 is the more common case.

[ Parent | on HN ]

Re:People suck at technical interviews (2014) by dagw on Friday June 10, 2016 @03:37PM (#11879341)

Or they're just using a bunch of SELECT * WHERE X queries and then filtering the results in their favorite programming language

[ Parent | on HN ]

Re:People suck at technical interviews (2014) by Thriptic on Friday June 10, 2016 @03:47PM (#11879436)

This. With smaller amounts of data it's not even a big deal. Just pull everything into python or R and subset in there.

[ Parent | on HN ]

Re:People suck at technical interviews (2014) by bobwaycott on Friday June 10, 2016 @03:41PM (#11879377)

That, too.

[ Parent | on HN ]

Re:People suck at technical interviews (2014) by golergka on Friday June 10, 2016 @05:47PM (#11880339)

But in #1 you're not working with SQL, you're working with a layer above it.

And wouldn't even the most basic data, properly normalized, require joins? I mean - learning about database normalization is one of the first things you're supposed to do when you work with relational databases, right?

[ Parent | on HN ]