<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: אהרון רוזנבוים</title>
    <description>The latest articles on DEV Community by אהרון רוזנבוים (@__8eb12836fd).</description>
    <link>https://dev.to/__8eb12836fd</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3650333%2F4ccefb9d-ebc6-4c11-8bef-6ff62d855380.png</url>
      <title>DEV Community: אהרון רוזנבוים</title>
      <link>https://dev.to/__8eb12836fd</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/__8eb12836fd"/>
    <language>en</language>
    <item>
      <title>Using n8n to Streamline Student Project Review – With Focus on OOP</title>
      <dc:creator>אהרון רוזנבוים</dc:creator>
      <pubDate>Sun, 07 Dec 2025 15:00:58 +0000</pubDate>
      <link>https://dev.to/__8eb12836fd/using-n8n-to-streamline-student-project-review-with-focus-on-oop-8lk</link>
      <guid>https://dev.to/__8eb12836fd/using-n8n-to-streamline-student-project-review-with-focus-on-oop-8lk</guid>
      <description>&lt;p&gt;Over the last semester, I explored how automation can improve the way we track and evaluate student projects, especially in structured programming courses like OOP.&lt;/p&gt;

&lt;p&gt;The challenge: Manually reviewing dozens of GitHub repositories, tracking submission dates, verifying file structures, and organizing feedback across multiple classes.&lt;/p&gt;

&lt;p&gt;The solution: I built a workflow with n8n, the open-source automation tool, that:&lt;/p&gt;

&lt;p&gt;Pulls data from student GitHub repos (via API)&lt;/p&gt;

&lt;p&gt;Analyzes key project files and folder structure&lt;/p&gt;

&lt;p&gt;Flags missing components (e.g. missing class implementations)&lt;/p&gt;

&lt;p&gt;Automatically labels each repo by topic focus (e.g. inheritance, polymorphism)&lt;/p&gt;

&lt;p&gt;Generates a summary report in Google Sheets or Notion&lt;/p&gt;

&lt;p&gt;Notifies me when new pushes are made after deadline 🚨&lt;/p&gt;

&lt;p&gt;🧠 Why it worked so well for OOP:&lt;br&gt;
The automation helped highlight how students applied principles like encapsulation and modular design. I could spot which projects followed proper class hierarchies — and which ones turned into spaghetti 😅&lt;/p&gt;

&lt;p&gt;Bonus: I had real-time visibility into class-wide patterns (e.g. 65% didn’t implement abstract classes correctly) — which helped adjust lectures and review materials.&lt;/p&gt;

&lt;p&gt;Tools used:&lt;/p&gt;

&lt;p&gt;n8n (self-hosted)&lt;/p&gt;

&lt;p&gt;GitHub API&lt;/p&gt;

&lt;p&gt;CoderByte &lt;/p&gt;

&lt;p&gt;Google Sheets&lt;/p&gt;

&lt;p&gt;This was just a prototype — but it sparked real excitement about using workflow automation in education.&lt;/p&gt;

&lt;p&gt;If you're managing technical coursework — or just curious about automating code review workflows — I highly recommend giving n8n a try.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8nbrightdatachallenge</category>
      <category>oop</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
