As for other areas, you know this is just one of the four parts of the exam, right?
As for other areas, you know this is just one of the four parts of the exam, right?
Software development is a big space with lots of room for specialization. Maybe it would be better, then, to model what is essential to "development" not as a distribution over knowledge but as a joint distribution over knowledge and specialization.
Since it's impossible to know everything about everything, it's really a question of "what is the probability that this will be useful?"
I think it's more a concern about a general attitude sometimes displayed on HN like "You don't know how X86 handles memory alignment, dude you even code?"
If you are focused on front-end work, knowing probability probably isn't going to change much.
That's certainly a valid hypothesis, but do we have any evidence to support it? I would be looking for causation, and not correlation (i.e. many great developers are familiar with calculus, because many great developers have CS degrees).
You seem to be saying that for certain values of k (e.g., k = “basic probability theory”), E[c(J,k)] is large enough that not having k qualifies a “deficit.” But the empirical evidence suggests that there’s a sizable set of respectable jobs X for which these deficits don’t matter. That is, for those exact same values of k, E[c(J,k) | J in X] is so small that the market effectively doesn’t care enough to withhold those jobs from people lacking k.
All of this is to say that when you say “software developers,” I think you’re imagining a set of people which is a lot narrower than the set the market actually maps to that job title. Today, “software development” admits a lot of jobs that don’t have a large dependence mathematics or computer science. The guys hammering out HTML and CSS all day long probably aren’t suffering for their probability-theory deficits. And yet most people do consider them software developers.
Question 3, for example, is obviously much more higher order math than the first spam question, but question 3 doesn't really have (IMHO) a damned thing to do with software development. The bigger question is whether calculus is a fundamental part of advanced software development, and the article does make an effort to indicate that it is, but I generally find that in a working environment there are a few math-oriented individuals, but most are more logic-oriented (which doesn't preclue math, admittedly), and unless you're on a project where higher-order math is required, you get along just fine. For those projects requiring physics calculations or whatever, you bring in the math geek. That doesn't mean it's not a testable question, but I contend it's not a requirement to be a damned good developer.