DenpaEnthusiast
No bio...
User ID: 131
DenpaEnthusiast
15d ago
It deserves to be erased.
DenpaEnthusiast
27d ago
I am skeptical of this paper's conclusions. For one, working memory and reasoning skills were twice as relevant as language skills, yet the paper focuses on language skills. Second, the paper contains sentences like "Critically, the existing research provides inconsistent evidence about the relevance of mathematical skills for learning to program" and "At the moment, the way in which programming is taught and learned is fundamentally broken", but the way they checked for mathematical skills was the Abbreviated Numeracy Scale, which is full of questions about specific numbers, like "A bat and a ball cost $1.10 in total. The bat costs $1.00 more than the ball. How much does the ball cost?". The math skills that are relevant to programming are about symbol manipulation, not numerical calculations. I would be a little surprised if essay-writing skill was a better predictor than probability-calculating skill was, but I would be very surprised if essay-writing was better than graph theory or logic. Third, numeracy was more correlated (albeit barely) than language with writing correct programs, which I would argue is more important than the other two categories (learning speed and the ability to answer quiz questions).
I doubt the study's claim that it "begins to paint a picture of what a good programmer actually looks like". To me it looks like the prose is motivated reasoning trying to obscure the actual data they collected, and the data they didn't collect but should have.
clean,checkout,reset, andrestore. You should be able to avoid this by not using them: every usage ofcheckoutcan be replaced by another command, and the others are specifically for discarding changes.push.autoSetupRemotetotrue. This will automatically create remote tracking branches on push. If you runpush,pull, orfetchwith no arguments they will automatically use your single origin.status --ignore-submodules=dirty. There's also the config optionsubmodule.<name>.ignore=dirty, but that needs to be set for each submodule. You can make that status command an alias if you don't want to type it out every time.commit -- file1 file2 .... You still need to explicitly stage any newly created files, and it won't work during merges.* merge=binary. If both branches have changes to a file, git will not modify the file, but will print an error saying there was a conflict and put it in the "unmerged paths" section of the status.More options
Context Copy link