<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Team on whois JoeByjo</title><link>https://joebyjo.dev/tags/team/</link><description>Recent content in Team on whois JoeByjo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 23 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://joebyjo.dev/tags/team/index.xml" rel="self" type="application/rss+xml"/><item><title>Getting GitHub updates on Discord</title><link>https://joebyjo.dev/posts/github_updates_on_discord/</link><pubDate>Mon, 23 Mar 2026 00:00:00 +0000</pubDate><guid>https://joebyjo.dev/posts/github_updates_on_discord/</guid><description>&lt;p&gt;I’ll be honest, I set this up because GitHub email notifications just weren’t cutting it. They’re delayed, easy to miss, and honestly a bit noisy.&lt;/p&gt;
&lt;p&gt;Instead of over-engineering a solution (which I was &lt;em&gt;very&lt;/em&gt; tempted to do), I went with the simplest possible approach:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Let GitHub send events directly to Discord using a webhook.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;No backend. No scripts. Just HTTP.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;p&gt;Before starting, make sure you have:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;GitHub account&lt;/strong&gt; with a repository&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;Discord server&lt;/strong&gt; where you can create webhooks&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="how-this-works"&gt;How This Works&lt;/h2&gt;
&lt;p&gt;At a high level:&lt;/p&gt;</description></item><item><title>Minesweeper 2.0</title><link>https://joebyjo.dev/projects/minesweeper2/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://joebyjo.dev/projects/minesweeper2/</guid><description>&lt;h1 id="reinventing-a-classic-building-minesweeper-20"&gt;Reinventing a Classic: Building Minesweeper 2.0&lt;/h1&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Few games are as iconic and deceptively simple as &lt;strong&gt;Minesweeper&lt;/strong&gt;. Beneath its minimal interface lies a game of logic, probability, and careful decision-making. However, while the original game is timeless, it leaves little room for variation or innovation.&lt;/p&gt;
&lt;p&gt;That’s exactly the challenge &lt;em&gt;Minesweeper 2.0&lt;/em&gt; set out to solve.&lt;/p&gt;
&lt;p&gt;The goal of this project was to reimagine the traditional Minesweeper experience by introducing powerups, while preserving the core logic-driven mechanics that make the game so engaging. Built using &lt;strong&gt;C++&lt;/strong&gt; and the &lt;strong&gt;SFML&lt;/strong&gt; graphics library, the project focuses on delivering a smooth, responsive, and visually intuitive desktop gaming experience.&lt;/p&gt;</description></item><item><title>Smartcourse Advisor</title><link>https://joebyjo.dev/projects/smartcourse/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://joebyjo.dev/projects/smartcourse/</guid><description>&lt;h1 id="smartcourse-advisor-merging-ai-data-and-student-voices"&gt;SmartCourse Advisor: Merging AI, Data, and Student Voices&lt;/h1&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Choosing the right university courses is a decision that can significantly shape a student’s academic journey, yet the process is often fragmented and overwhelming. Students typically rely on scattered sources such as informal reviews, outdated course guides, or trial-and-error when planning their degree.&lt;/p&gt;
&lt;p&gt;This challenge becomes even more relevant in the context of institutional change, such as the &lt;strong&gt;University of Adelaide&lt;/strong&gt; merger, where navigating course options can become even more complex.&lt;/p&gt;</description></item></channel></rss>