TL;DR
This paper identifies robot-specific coding patterns in block-based programming for educational robots, enabling automatic feedback to improve learning and code quality.
Contribution
It introduces a set of robot-specific bug patterns, code smells, and good practices for mBlock programs and extends an analysis framework for automatic detection.
Findings
Detected 6,129 bug pattern instances in dataset
Identified 592 code smells indicating confusing code
Found 14,495 code perfumes suggesting good practices
Abstract
Programmable robots are engaging and fun to play with, interact with the real world, and are therefore well suited to introduce young learners to programming. Introductory robot programming languages often extend existing block-based languages such as Scratch. While teaching programming with such languages is well established, the interaction with the real world in robot programs leads to specific challenges, for which learners and educators may require assistance and feedback. A practical approach to provide this feedback is by identifying and pointing out patterns in the code that are indicative of good or bad solutions. While such patterns have been defined for regular block-based programs, robot-specific programming aspects have not been considered so far. The aim of this paper is therefore to identify patterns specific to robot programming for the Scratch-based mBlock programming…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
