This was taken at noon on 19 December 2024 while I was compiling the errors and solutions from the assembly code that students encountered during the Microprocessor class the day before.
This serves as a diagnostic report after allowing the students to use their own laptops to compile the assembly code from Modules 8 and 9. I had provided the necessary steps to the students in class and encouraged them to work on it within their respective groups. Initially, I was instructed to demonstrate the process in class, but I felt it would be more beneficial for the students to try it themselves—and this decision proved to be correct.
From the diagnostic report, it became clear that 98% of the students made the same basic mistake: failing to save the project file in a newly created folder. Despite this, 9 groups were able to successfully resolve their errors, 1 group is still struggling, and another 6 groups have yet to provide any updates on their progress. Failure to submit updates will, unfortunately, result in no marks for the class exercise.
Preparing this kind of report is tedious and time-consuming. However, if it’s not done promptly after the class, it’s easy to forget the details by the following week. That said, documenting these errors and solutions is a great practice for self-improvement and professional development. Of course, this approach may not work for everyone, as individuals have their own methods of handling such tasks.
Until next time, have fun creating diagnostic reports after each session!
Reference:
No comments:
Post a Comment