References

• https://uwaterloo.ca/centre-for-teaching-excellence/teaching-resources/teaching-tips/developing-assignments/cross-discipline-skills/teaching-problem-solving-skills
• https://runestone.academy/runestone/static/thinkcspy/index.html
• https://www.cs.utah.edu/~germain/PPS/Topics/problem_solving.html
• https://www.codeproject.com/Tips/833768/The-Beginner-Programmers-guide-to-Problem-Solving
• https://codeburst.io/10-steps-to-solving-a-programming-problem-8a32d1e96d74
• http://www.ics.uci.edu/~kay/courses/31/design-recipe.html
• https://www.coursera.org/learn/duke-programming-web/lecture/AEy5M/a-seven-step-approach-to-solving-programming-problems
• https://cs61a.org/resources.html
• https://docs.google.com/document/d/1Yw6wK6PPL7x7wJB6Wo9qkWz8rgJwo-t0cXU5pFstaVA/edit
• https://ericlippert.com/2014/03/05/how-to-debug-small-programs/
• https://stackoverflow.com/help/how-to-ask
• http://buildingskills.itmaybeahack.com/book/programming-2.6/html/p14_finish/p14_c03_professionalism.html
• http://buildingskills.itmaybeahack.com/book/programming-2.6/html/appendices/debugging.html
• http://www.oxfordbibliographies.com/view/document/obo-9780199756810/obo-9780199756810-0084.xml
• https://en.wikipedia.org/wiki/Design_by_contract
• https://curriculum.code.org/csd-18/
• https://www.cultofpedagogy.com/holistic-analytic-single-point-rubrics/
• http://saja.kapsi.fi/var_roles/
• http://42cs.github.io/book/
• https://standards.ieee.org/standard/610_12-1990.html
• https://6009.cat-soop.org/
• http://web.mit.edu/6.031/www/
• https://pragprog.com/book/tpp/the-pragmatic-programmer
• https://jupyter4edu.github.io/jupyter-edu-book/
• https://users.ece.utexas.edu/~adnan/pike.html
• http://www.lysator.liu.se/c/pikestyle.html
• https://programbydesign.org/
• https://fopp.umsi.education/runestone/static/fopp/index.html
• Woods, D. R. (1987). How might I teach problem solving?. New Directions for Teaching and Learning, 1987(30), 55-71.
• Loksa, D., & Ko, A. J. (2016, August). The role of self-regulation in programming problem solving process and success. In Proceedings of the 2016 ACM Conference on International Computing Education Research (pp. 83-91). ACM.
• Loksa, D., Ko, A. J., Jernigan, W., Oleson, A., Mendez, C. J., & Burnett, M. M. (2016, May). Programming, problem solving, and self-awareness: effects of explicit guidance. In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems (pp. 1449-1461). ACM.
• Robins, A., Rountree, J., & Rountree, N. (2003). Learning and teaching programming: A review and discussion. Computer science education, 13(2), 137-172.
• Sorva, J. (2013). Notional machines and introductory programming education. ACM Transactions on Computing Education (TOCE), 13(2), 8.
• Sorva, J. (2012). Visual program simulation in introductory programming education. Aalto University.
• Guttag, J. V. (2013). Introduction to computation and programming using Python. Mit Press.
• Papert, S. (1980). Mindstorms: Children, computers, and powerful ideas. Basic Books, Inc..
• Spraul, V. A. (2012). Think Like a Programmer: An Introduction to Creative Problem Solving. no starch press.
• Barr, A. (2004). Find the Bug: A Book of Incorrect Programs. Addison-Wesley Professional.
• Zeller, A. (2009). Why programs fail: a guide to systematic debugging. Elsevier.
• Butcher, P. (2009). Debug it!: Find, repair, and prevent bugs in your code. Pragmatic Bookshelf.
• Knuth, D. E. (1989). The errors of TEX. Software: Practice and Experience, 19(7), 607-685.
• Ko, A. J., & Myers, B. A. (2003, October). Development and evaluation of a model of programming errors. In Human Centric Computing Languages and Environments, 2003. Proceedings. 2003 IEEE Symposium on (pp. 7-14). IEEE.
• Hermans, F., Swidan, A., & Aivaloglou, E. (2018, May). Code Phonology: an exploration into the vocalization of code. In Proceedings of the 26th Conference on Program Comprehension (pp. 308-311). ACM.