-
-
This is our Pawpilot logo
-
This is David and Hudson after they finally got their program to work following 9 hours of coding.
Inspiration
-Extremely high dropout rates in my initial fundies class -Disparity in the socioeconomic backgrounds of people who got into coding -Saw that teachers worked extremely hard but didn't always have enough time to help each individual student
What it does
-Our website is broken down into 3 simple features Explanation Resources Review -The first step allows users to paste in starter code from the teacher, it breaks it down into manageable steps teaching the students how to turn a large problem into a simple step. -The second step gives users easy access to resources for any assignment they are working on. It is not generally taught in depth how to find resources so this helps beginners get a great initial step. -The final step reviews the users code and provides feedback. This can be in the form of strengths/weaknesses, how to make the code more efficient, things to consider for next time. Essentially the "take away" feature allowing students to understand what they learned and go over it with a personal "tutor".
Our roles
-David Xiao: Full Stack Developer -Hudson Kass: Full Stack Developer -Caleb Harper: Front-End Developer
How we built it
-We split our project into 2 parts, front-end and back-end. David and Hudson initially did our research on the GPT API and how to call custom GPT's from the backend while Caleb started researching for the website. -We used node.js to run the backend with html and CSS for our website -We spent hours on the documentation trying to learn and understand it before we even saw any progress.
Challenges we ran into
-The OpenAI API was extremely complicated for David and Hudson to figure out as they have not had much back-end experience before. -Our group initially tried to make a chrome extension but later learned it wasn't able to integrate the OpenAI API -Half of the team was not able to work due to unforeseen circumstances so David and Hudson had to complete the back-end on their own and the front end with Caleb. -Disagreements occurred but our group was always able to compromise after some discussion
Accomplishments that we're proud of
-Getting to integrate the API with each of the 3 features on our website -Making the website look clean and modern -Making our project easy to understand/learn -Our project actually solving a real problem in this world, especially one that touches our community
What we learned
-We learned to always expect the unexpected -Things get worse before they get better -We found help in the most unlikely of places (GSB at 4am) -When stuck take a short break and then come back to the work -It is good to come in with a plan before you start
What's next for Pawhacks CHMD
-Not just hosting it locally but hosting it on the web 24/7 so anyone can access -Integrate and make assistants better -Make our own coding assistant that dynamically helps as a user codes -Pairing up with faculty to help promote coding to everyone
Log in or sign up for Devpost to join the conversation.