{'fraction_non_alphanumeric': 0.015031645569620253, 'fraction_numerical': 0.0, 'mean_word_length': 4.802752293577981, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Just because we teach it does not mean they use it: Case of programming skills

We are assessing the effect of our new freshman electrical engineering course sequence on follow-on courses. One of our assessments is a survey distributed to sophomores in electrical circuits and juniors in microelectronics courses. Roughly one half of freshman year is spent on programming in MATLAB and C, and problem solving using these programming tools. Our observation is that students consider programming important and have reasonably good confidence (self-efficacy) that they can solve problems using MATLAB and C. However, when asked about frequency of use for these tools students report using them somewhere between once a week and once a month. There is a significant number of students who report almost no usage at all. Results are consistent across sophomore and junior years with a slight up-tick in frequency of use for juniors. We are hypothesizing that students do not view MATLAB and C as tools for problem solving but as yet another item to acquire in their studies. Our plan is to change instruction in sophomore courses so that more problem-solving which requires programming will be introduced. The existing survey will be used to measure future improvement.