Answers are grounded in this paper and cite their sources.
The article considers a distinct class of programming tools mastered in teaching through robotics — infrastructure development tools. It is argued that, alongside programming languages and environments, competitive robotics activity requires command of the tools that enable development itself: the command-line interface, a documentation markup language, a version control system, a data query language, and tools for scenario automation and containerization. These tools usually remain outside the school informatics course, whereas team-based and reproducible development, as well as competition regulations, make them a necessary object of learning.A classification of infrastructure tools by their function in the program development cycle is proposed and summarized in a registry indicating representatives and the level of introduction. The methodology of introducing each class of tools is described, tied to the stages of instruction and to the tasks of the competitive field: microcontroller programming and working with sensor libraries, maintaining an engineering journal, collaborating on shared code, processing robot telemetry, integrating sensors with network services, and ensuring the reproducible launching of the solution. A regularity is shown: tools are introduced following the increasing complexity of the student's activity — from individual program launching to team development and reproducible integrated solutions. The article is addressed to informatics teachers, supplementary-education teachers, and organizers of competitive robotics training.
No takes yet. Share an insight, caveat, or question.
M. V. Myradov (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: