I primarily use Git as a backup for my own website stuff. But besides that it is a convenient backup, it can also be used to track changes on a project, or easily work with multiple people on the same project. An example of this is the Git of the group project. Portfolio Git repo

In this group project, I was mainly active in the development of the final product. So when I got to work on the HTML and the CSS, I kept pushing my changes. With every push I did to the server, I needed to give the commits sensible descriptions. This way, if something would turn out to not go so well, we can backtrack when I worked on what element. I haven't really worked on branches yet, as we as a group agreed that when I needed to work on it they didn't have things they wanted to do on it. I did call in the help from Max for a couple animations, which he implemented in the CSS, pushed, and then I “merged” my version with his. But as our changes were many lines apart, there were no merge conflicts and everything merged properly.

Prism Git repo

As the most that I have put on Git is just a website, I don't really have a Git Readme for it. I did add a very small intro on what the Git contains, and how to be able to “use” it, but for the rest I haven't done a lot with it though. I did try out making a Readme with ChatGPT though, which came with a whole template that can be used directly in the right format. So that is a really usable tool to get templates for such things.

I like keeping my code organized. However I sometimes forget to comment every piece of code as I'm still trying things out to see what it does, or I'm in a flow of purely adding code. This unfortunately leads to me having to reverse-engineer my own code, when I want to change something. An example of this is when I wanted to make “glitchy page”. I wanted to add several effects that would give the illusion that something is massively wrong with the website. I have added several effects, gave the functions reasonable and sensible names, so that did make it easier to change things later as the name did remind me of what it did again. But a line of comment would have been nice, which is why I now also implemented that.

For the work we did as a team, we mainly worked in Teams. We did encounter some small synchronization issues when we tried working on the same file inside Teams itself, but when we then opened it in the dedicated app, like Word, everything worked well. We also used Figma, where we could all work on the same project file at the same time. another tool we used multiple times was Trello, to have a sort of shared pinboard of tasks we need to do. for the communication we mainly use WhatsApp, and sometimes a little bit of Teams.