What We Learned and Experienced During the Hackathon

1. Learning Three.js

Through this project, we learned how to create a project using Three.js. Before this hackathon, none of us had ever built a Three.js project.

Even before the hackathon started, we had already planned to build this game. We spent time researching how to set up Three.js projects, how web-based games work, and how to approach game development in the browser.

We already had a pretty good understanding of the backend because this was not our first project. This was approximately our fourth hackathon, and we are also working on our own projects. So, we were familiar with most of the technical concepts involved. However, Three.js was something completely new for us.

2. Building and Collaborating with Trimi

The building phase with Trimi was a good experience, especially because we were working together on the same project.

In our previous projects, we often faced collaboration issues. For example, when one person was working on the frontend and another was handling the backend, we had to follow a process:

The frontend developer had to push their code to GitHub.
The backend developer had to download or pull the latest code.
Then they could understand the frontend structure and integrate their part.

This process sometimes slowed us down.

For this project, we created separate branches within the same project. This allowed both of us to work independently on our respective parts while still being able to view and understand each other's code without having to download the entire project.

This made collaboration much smoother and helped us avoid many of the issues we had experienced in previous projects.

3. Credit Usage

We built the entire project using our available credits.

My initial credits: 1,000
Credits remaining: 200
My friend's credits: 1,000 (unused)

Our initial plan was to switch to my friend's account if my credits ran out. However, we did not need to do that because we were able to complete most of the work using my credits alone.

Overall, the experience helped us learn a new technology, improve our collaboration workflow, and build a game using a technology we had never worked with before.