CodeGrade Logo

Blog

Keep up with the latest releases and developments.

  • CodeGrade screencast series - CodeGrade Filesystem

    Background Features

    By: Devin Hillenius (Founder, Business Development and Partner Success)

    In the new CodeGrade screencast series, we are showcasing and explaining CodeGrade’s most important features in weekly videos.

  • CodeGrade screencast series - Plagiarism Detection

    Background Features

    By: Youri Voet (Founder, Business Development and Partner Success)

    In the CodeGrade screencast series we showcase and explain the most important features in CodeGrade.

  • CodeGrade screencast series - Inline Feedback

    Background Features

    By: Devin Hillenius (Founder, Business Development and Partner Success)

    For the past couple of weeks we have been working on a new screencast series in which we will showcase and explain CodeGrade’s most important features.

  • Relieving workload on teachers and improving feedback for students

    Background

    By: Youri Voet (Founder, Business Development and Partner Success)

    As many students and teachers experience, learning to code is hard and challenging. It is a skill that needs to be learned by doing, and a skill that is learned by making mistakes and learning from these mistakes. Without sufficient feedback, however, it is challenging for students to know how and where to improve, and it might impair their motivation too.

  • Our Story

    Background Team

    By: Devin Hillenius (Founder, Business Development and Partner Success)

    Almost two years ago, we started developing the very first version of CodeGrade as part of a course in our Computer Science bachelor at the University of Amsterdam. The idea for a blended learning tool to improve programming education emerged from our own frustrations as students and teaching assistants at the university. We thought the feedback we got on our assignments, if we even got any feedback at all, was inadequate and did not effectively made us learn from our mistakes. Later, as teaching assistants, we found out that the amount of overhead and lack of efficient and code-specific tools made it almost impossible to provide sufficient feedback or to check for plagiarism.