A test which predicts ability to program before the start of training
eis.mdx.ac.uk
eis.mdx.ac.uk
http://crpit.com/confpapers/CRPITV78Bornat.pdf
We now report that after six experiments, involving more than 500 students at six institutions in three countries, the predictive e ffect of our test has failed to live up to that early promise.
Meta-analysis of the effect of consistency on success
in early learning of programming is our fourth paper
that was presented to Psychology Programming Interested
Group (PPIG) Annual workshop on July 2009.
Abstract: ... The test does not very accurately predict
levels of performance, but by combining the
result of six replications of the experiment,
five in UK and one in Australia. We show
that consistency does have a strong effect
on success in early learning to program but
background programming experience, on the
other hand, has little or no effect.
In short, the jury is still out, but there is some sort of effect showing up, and it's going to need careful experiments to find out what's really going on. It does seem to show promise, though, of finding a predictive effect.
http://news.ycombinator.com/item?id=1145654
Edit after kind reply by Colin:
I think the earlier discussion was especially valuable because of a checklist of factors to look at in further research offered by one of the HN participants who commented there.
http://news.ycombinator.com/item?id=1146044
Here in this discussion that began today, in another reply, a participant posted
it seemed like there was a "programming gene" (not literally) that gave some people innate ability, and without this you were sunk.
Some kind of "nature" explanation is what the human mind jumps to as an explanation of individual differences, by innate human cognitive biases. To tease out causation in such a matter would take what Robert Plomin and other behavioral geneticists call a "genetically sensitive" study design, which is lacking here. But there is such a huge body of human behavioral genetics research already, that I can confidently predict what the finding would be for anything properly called "programming ability":
1) Programming ability will be found to be heritable, that is that it shows tighter correlations among closely related persons than among distantly related persons, because all human behavioral characteristics are heritable,
and
2) programming ability is still exquisitely sensitive to environmental influences (which perhaps are not well understood), especially influences of "nonshared environment," the kind of environmental variation that results in siblings brought up in the same household differing from one another.
A reference for both general propositions that is well worth reading is
http://people.virginia.edu/~ent3c/papers2/Articles%20for%20O...
Johnson, W., Turkheimer, E., Gottesman, I. I., & Bouchard, T. J. (2009). Beyond heritability: Twin studies in behavioral research. Current Directions in Psychological Science, 18, 217-220.
Some might cheer and say "Ha! Auto-hoist, petard-wise," but this latest submission points to the page that documents the continuing saga. They have addressed many of the criticisms leveled at the paper in the submission wo which you refer, and carried out both further studies and a meta-analysis.
Hence I thought it worth re-visiting.
Having said that, the discussion on that submission is definitely worth reading.
I observed the "double hump" in an intro computer science class I took in college. Out of 20 people in the class, only 3 had prior programming experience. As the semester progressed, some were able to learn basic Java while others were not; aptitude seemed to be fairly independent from both effort put into this class and performance in other courses.
Since then, I've wondered why this was the case -- it seemed like there was a "programming gene" (not literally) that gave some people innate ability, and without this you were sunk.
It seems like there would be more research on phenomena, but this is the first work I've seen that hypothesizes why this happens.
In my own case I disliked Java so much in my first year of University because I couldn't understand why there was so much effort just to get this little black screen to print "Hello, World."
I would go on but I actually already wrote about this a couple years ago on Reddit: http://www.reddit.com/r/programming/comments/84c90/i_fear_as...
This was in 2009, so today's obvious alternatives to Java (Ruby or Python) were not as popular.
However, it should be noted that for the course I mentioned, the friction of getting started in Java was not an issue: there were only 20 people in the class and we all lived in the same dorm so people could get help when they needed it.
I've observed that most people do not demonstrate this ability. An example, while doing a consulting gig for a large agro-business a few years ago they wanted to solve a single question
"should we brand our new product with verbiage about it being all natural?"
Helping them resolve this question involved coaching a dozen very well educated people through a simple process of functionally breaking this question down into solvable sub-components.
"how do consumers feel about the term 'all natural'?" ->
("how can you find out?", "are there equivalent valid terms we can test?") ->
(("do you have data that represents a consumer voice?", "is there a way to process this data to find sentiment?"), ("who in your company might know equivalent industry terms?", "can we ensure the regulations around these equivalent terms allows us to use them in this case?")) ->
((("lets get data from site A, B and provider C", "let's use these tools and techniques to extract terms, timeline the usage and score for sentiment"), ("let's meet with these folks and collect there terms and use them in the above process", "send the top 3 results to legal for regulation confirmation")
Basically just keep breaking down the questions become so trivial they basically solve themselves.
This was a revolution to them. The only method they were aware of to answer the question above was to blanket shopping malls with market survey teams at a very high cost. People in general tend to think of establish procedure not in functional decomposition and problem solving.
I've observed that this holds true for nearly everybody I've encountered who couldn't learn to program. This kind of problem solving technique was something that they simply hadn't learned to do and it's exactly what you have to do to learn to program.
"I need to write a program to do X, how do I do X?" they need to learn to break that problem down into smaller and smaller pieces until those pieces become orthogonal with the language they need to use. X might be made up of 1000 sub-components, and arriving at those is simply a matter of dividing X down in a series of phases, asking "can I answer this with the language I know yet?"
Even people who do fine in other classwork, say they breeze through calculus, aren't taught this and as far as I know it's simply not taught in academic situations outside of some of the more formal maths (e.g. any math where you spend more time with proofs than mechanical problem solving) because schools teach via composition instead of decomposition (or synthesis instead of analysis).
What I mean is that schools start from first principles, in the maths it'll be axioms and mechanics, in history it's ancient history, in language it'll be simple reading and writing skills, etc. and build up to some standard. But at no point are people taught to take a complex problem and break it down into more simply solvable sub-components. This is exactly the kind of skill that people need to learn to program and IMHO should be the entire first year of any degree program that requires programming of any sort.
The beauty of course is that if you can't break something down further, and you don't know how to solve it, it's probably solvable with a technique you simple don't know at that point...and that's where education can slot in.
Even various systems/enterprise Architecture classes don't quite view the world this way. Sure you start with a high level problem, but very quickly you find yourself building up a solution rather than functionally decomposing the problem down to easily solvable atoms.
For example:
Problem: "Design an enterprise system for a company that meets these high level abstract goals"
Solution: Fill out the TOGAF framework.
http://en.wikipedia.org/wiki/Operations_research#Second_Worl...
http://en.wikipedia.org/wiki/Systems_analysis#Overview
http://en.wikipedia.org/wiki/Decision_tree#General
http://en.wikipedia.org/wiki/Decomposition_%28computer_scien...
But I'm wondering if we're just doing this all wrong. If this kinda of mental technique shouldn't be taught very early in many disciplines...maybe even as early as elementary school.
It's not to say we should abandon the bottom up approach in use today, it's very useful for understanding many subjects. But there's very little done from a top-down style approach I'm thinking of...and it gives us a deficit in people who are unprepared for learning programming or similar disciplines later on.
I've met programmers who can't do this, and they were really bad... Suitable only for mindless tasks where they were given all the logic and just had to key it in and test it.
There's reasons to think there's a lot of scope for improvement.
For a very general reason: that we don't really know that much about how our brains and thinking work. Once we do we are likely to be much better at identifying precisely why some people are poor at certain tasks, and at knowing how to train people to improve their skills at those tasks.
[EDIT: wording]
I almost cracked up at this. As much as we'd like to say that's how we behave, I'd say just about all of us are more likely to try to answer anyway.
Of course this mental model makes all questions trivially easy, for example:
"Question 12": int a = 5; int b = 3; int c = 7; a = c; [a becomes the value 7 permanently] c = b; [c becomes the value 3 permanently] b = a; [b becomes the value 7 permanently] a = 7; b = 7; c = 3
If I had picked a different mental model by chance that was more complicated for my working memory, I find it quite likely that I would have made some careless mistakes. So maybe some participants were not incapable of forming a consistent mental model, but picked a very hard mental model to start with?
I've seen people not be able to answer these questions, even after a term of CS. :c
Two years ago I was tutoring a young lady that had a serious passion for programming, it was what she talked about constantly, and she was in college taking a number of beginning courses in programming. She studied day in and day out, working countless hours every night trying to "practice being a programmer". She did every exercise given in the text books, and even had a number of other textbooks on VB.NET (the language being taught in the course.) and she studied them for hours every night. At the end of two semesters she still could not program anything if the steps to the goal were not outlined for her. She could recite to you the syntax of VB.NET and many of its companion (.NET) libraries by heart, she could tell you what a piece of code did when she looked at it (she was strangely adept at reading code and knowing what it did) but to ask her to come up with the required steps to sort an array of numbers from highest to lowest and her brain simply could not break down the logic to a point where she could write it herself.
I also tutored a young fellow last fall that was in a similar predicament. He was trying to pass a basic programming course so he could get an IT diploma and this one beginner programming course was a requirement for this diploma. He was driven to study, and was willing to put forth the effort to get through this course, and he most likely would have (given multiple choice options been) able to see the pattern. On the other hand ask him to assign the value of “b” to ”a” and he would start to get lost. Ask him to assign “b” to “a” and “a” to “c” and “d” to ”b” and he completely shuts down. No matter how many examples he was given, no matter how hard I tried to show him alternate ways of looking at it, the act of assigning values to variables and then interacting with those variables to manipulate the values just would not stick.
My opinion after dealing with a number of others like these two students is that some people lack the ability to develop patterns. Not necessarily to see patterns, but to come up with their own. They tend to have poor visualization skills and they tend to find it hard to understand the pattern links when given something like an analogy. I would say that the ideas behind encapsulation and inheritance stem from assignment but they look at larger assignment patterns than a simple a = b. Thus, if the individual lacks the basic ability to conceive the pattern of assignment required to get to the goal of the code they are not able to learn the ability to program.
O.
Hard work. Too many students just won't do the work. They'll show up, go thru the motions, rattle something passable into place, and wonder why they didn't pass (or almost didn't). The work has to go beyond just what is required into self-motivated learning beyond.
Grokking variables. Many don't comprehend the nature of a variable, and thus cannot succeed in using them. They know the right things to say about variables, and may achieve passable results using them, but just don't get the concept.
Task decomposition. Many can't get past "just do it", viewing the term as an end instead of a beginning.
Strict adherence to rules. Whatever the rules of syntax are, that's what you have to work with, and deviation just doesn't work.
Semantics. One must be capable of realizing that certain phrasing influences perception.
Abstraction. Many can't.
Get those down and you'll learn. Miss one or more and it will be very hard.
It's not a very motivational message but I really believe some types of thinking are beyond the reach of certain people, due to the physical (read genetically determined) constraints on their brain.
Of course, ideally, this would be something everybody comes out of high school with, and most of the top hump have probably intuited this from math classes. Looking at my kids' curricula, though, there is nothing explicitly trying to teach these concepts.
I have no hard data to back this up, save for my own observations.
Consider something like language acquisition for example; if you had a 30 year old that already knew 3 languages they would almost certainly perform better on an exam to test potential to learn new languages than a 30 year old that knew one language.
If I am reading you correctly you are saying "that's not actually a legitimate potential predictor; it just indicates what experience you have, not a true measure of your capability going forward", but in reality if you have only learned one language by the time you are 30, you are at a point where your gene pool is not a great predictor. By the time you are 30, your lack of previous experience has actually had a physical effect on your brain that prevents you from being as good at language acquisition going forward.
It's not merely the fact that you have experience in a particular area that improves your direct ability to answer questions; lacking experience actually makes it more difficult to acquire the same levels of experience.
In other words, having experience makes you more able to gain experience; a test that measures your experience is a legitimate indicator of future learning potential. It's exactly along the line of colleges teaching you "how to learn" and any practical skills that you gain along the way are largely incidental.
Indeed! Combine several tests of mental potential into an omnibus test, and run a large group of people through the omnibus. If you run the results through common factor analysis, you will find that getting a good score on one subtest is highly correlated to getting a good score on each of the other subtests. Psychologists have named the common underlying cause g, the general intelligence factor. (Scaled for age and population variation, g becomes an IQ score.)