3 ms·

Any time you attempt to divide a group like this into two categories, you pretty quickly find that each of the sub categories have pretty obvious subdivisions,

Any time you attempt to divide a group like this into two categories, you pretty quickly find that each of the sub categories have pretty obvious subdivisions, and each of those subdivisions have some obvious divisions that span all of the other divisions. It would be more productive to simply assign attributes to people, and allow all combinations of those attributes. For example, there are people who have a formal CS education, and those that don't. There are those that have a good grasp of data structures and their applications and those that don't. Those groups have overlap, but not 100%. If you want to argue that people should have some particular fundamental skill, say that particular skill instead of an abstraction (A CS degree, or 'fundamentals'). We have all met people with CS degrees that couldn't solve a simple CS problem, and we have all met the inverse. From a practical perspective, you need both the fundamental skills that a task requires as well as the skills to use the tools.

aranw 6y ago
I tend to understand a lot of this stuff but the issue I struggle with the most is remembering it all off the top of my head which is what usually is my biggest weakness when entering technical interviews and when I start getting asked questions about this stuff. I hate studying before such events to make it look like I do remember or know this stuff I'd rather be up front and honest and say I got a high level overview of this or I haven't studied that in awhile but I know X, Y and Z about it. I really hate this idea that everyone should just know all this stuff and study on it all the time
- sponaugle 6y ago
  In my mind, a good interview should be able to allow you to have google open, books, etc, if that is a tool you use. Knowing what you memorized hasn't been a good indicator for performance in my experience. I have done almost 1000 interviews in my career, and most of what I have asked about in an interview has turned out to be a poor indicator of success.
WiseWeasel 6y ago
You’ll need to remove the space padding in those parentheses to get this PR merged. [resolved]
l0b0 6y ago
Basically, human complexity means that tagging >> categorization.

aranw 6y ago

I tend to understand a lot of this stuff but the issue I struggle with the most is remembering it all off the top of my head which is what usually is my biggest weakness when entering technical interviews and when I start getting asked questions about this stuff. I hate studying before such events to make it look like I do remember or know this stuff I'd rather be up front and honest and say I got a high level overview of this or I haven't studied that in awhile but I know X, Y and Z about it. I really hate this idea that everyone should just know all this stuff and study on it all the time

sponaugle 6y ago
In my mind, a good interview should be able to allow you to have google open, books, etc, if that is a tool you use. Knowing what you memorized hasn't been a good indicator for performance in my experience. I have done almost 1000 interviews in my career, and most of what I have asked about in an interview has turned out to be a poor indicator of success.

WiseWeasel 6y ago

You’ll need to remove the space padding in those parentheses to get this PR merged. [resolved]

l0b0 6y ago

Basically, human complexity means that tagging >> categorization.