Interesting insight from a huge round if interview...

# random

[apatrida]

Interesting insight from a huge round if interviewing with programming challenges. People who know Java or C# then decide to pick Python or JavaScript for the challenge part because they feel like they are "faster" or "easier" to throw something together.

then they end up not knowing they have "Map" or "Set" available, start returning data in non descriptive function returns, don't think of a JSON object as a map/dictionary, can't copy a two dimensional array without reading 10 ways of how to do it on stack overflow that argue about performance and the right way, can't figure out how to deal with a JSON (or dictionary) were they don't know the keys ahead of time, can't iterate the entries in a dictionary/JSON/Map, and so on.

"easier" and "faster" hmmm. "easier" becomes "what did I just write?!?" and "faster" becomes "shit, how do I..."

[Andreas Sinz]

apatrida: they must do real programming challenges as part of an interview?

[apatrida]

small but touch realistic skills.