Voice-Assisted Multimodal Debugging and Comparative Analysis of Python Applications in Visual Studio Code and PyCharm
DOI:
https://doi.org/10.63503/acset.112Keywords:
Voice-Assisted Debugging, Multimodal Systems, Python Debugging, Visual Studio Code, PyCharm, Software Debugging, Cognitive Load Reduction, Error Analysis, Integrated Development Environments, Performance EvaluationAbstract
Software debugging is a crucial but lengthy process in software development that may require developers to decode complicated error messages and stack traces. The growing complexity of Python applications today underscores the need for more intuitive and effective debugging methods. This paper focuses on enhancing debugging effectiveness by presenting a voice-assisted multimodal debugging system. This work is valuable because it helps reduce cognitive load and improve accessibility, particularly for developers who have difficulty with traditional text-based debugging techniques. Current debugging tools in integrated development environments like Visual Studio Code and PyCharm are mostly visual, which can slow error understanding and increase cognitive load. These solutions are not multimodal and are not able to accommodate the needs of different users. The aim of the study is to develop and test a system that combines voice feedback and visual debugging to enhance understanding of errors and overall productivity. The suggested system will present a voice-assisted debugging system that records the runtime exceptions and provides audio and graphical feedback, as well as smart recommendations. Experimental evidence shows that the system is also faster at identifying errors and gives a more user-friendly debugging experience in both development environments. Also, the approach offers benefits such as lower cognitive load, greater accessibility, and increased resource awareness through comparisons of IDE performance.
References
[1] H. Li and M. Coblenz, “A Grounded Theory of Debugging in Professional Software Engineering Practice,” arXiv preprint arXiv:2602.11435, 2026.
[2] F. Stolp et al., “Using CognitIDE to Capture Developers' Cognitive Load via Physiological Activity During Everyday Software Development Tasks,” arXiv preprint arXiv:2503.03537, 2025.
[3] A. C. Tajimalela et al., “Comparison Towards Different Methods of Software Debugging,” Journal of Software Engineering, Information and Communication Technology, 2024. :contentReference[oaicite:0]{index=0}
[4] X. Gao and K. F. Hew, “A Flipped Systematic Debugging Approach to Enhance Program Debugging Performance and Optimize Cognitive Load,” Educational Technology Research and Development, 2023. :contentReference[oaicite:1]{index=1}
[5] C. Sun, S. Yang, and B. Becker, “Debugging in Computational Thinking: A Meta-analysis on the Effects of Interventions on Debugging Skills,” Journal of Educational Computing Research, 2024. :contentReference[oaicite:2]{index=2}
[6] R. McCauley et al., “Debugging: A Review of the Literature from an Educational Perspective,” Computer Science Education, vol. 18, no. 2, pp. 67–92, 2008. :contentReference[oaicite:3]{index=3}
[7] M. Lanza, R. Robbes, and M. Lungu, “Patterns of Developers’ Behaviour: A 1000-Hour Industrial Study,” Journal of Systems and Software, 2017.
[8] I. A. Khan, W. P. Brinkman, and R. M. Hierons, “Do Moods Affect Programmers’ Debug Performance?” Cognition, Technology & Work, vol. 13, no. 4, pp. 245–258, 2011. :contentReference[oaicite:4]{index=4}
[9] S. Shrivastava, S. Maurya, and A. Kumar, “Debugging Behavior in Software Engineers Based on Personality Dimensions,” TPM – Testing, Psychometrics, Methodology in Applied Psychology, 2025. :contentReference[oaicite:5]{index=5}
[10] A. Mohammed et al., “An Empirical Eye-Tracking Study of Program Comprehension and Debugging,” Information and Software Technology, 2026. :contentReference[oaicite:6]{index=6}
[11] M. A. Storey et al., “How Do Programmers Understand Code? A Survey of Program Comprehension,” IEEE Transactions on Software Engineering, 2005.
[12] R. Mohanani et al., “Cognitive Biases in Software Engineering: A Systematic Mapping Study,” IEEE Transactions on Software Engineering, 2017.
[13] A. Z. Henley and S. Fleming, “Cognitive Load While Debugging: An Empirical Study,” IEEE Symposium on Visual Languages and Human-Centric Computing, 2016.
[14] B. A. Myers et al., “The Debugging Process and Its Challenges: A Human-Centered Perspective,” Communications of the ACM, 2016.
[15] R. S. Pressman, “Software Engineering: A Practitioner’s Approach,” McGraw-Hill, 2014.
[16] T. Fritz et al., “Using Psycho-Physiological Measures to Assess Task Difficulty in Software Development,” ICSE, 2014.
[17] A. J. Ko and B. A. Myers, “Debugging Reinvented: Asking and Answering Why and Why Not Questions,” ICSE, 2008.
[18] G. Murphy-Hill et al., “How We Refactor, and How We Know It,” IEEE Transactions on Software Engineering, 2012.
[19] F. P. Brooks, “The Mythical Man-Month: Essays on Software Engineering,” Addison-Wesley, 1995.
[20] “Hear Your Code Fail: Voice-Assisted Debugging for Python,” 2025.
Downloads
Published
Conference Proceedings Volume
Section
License
Copyright (c) 2026 Adroid Conference Series: Engineering and Technology
This work is licensed under a Creative Commons Attribution 4.0 International License.
