One of the obligatory assignments for the Advanced CSS course. The purpose of the assignment was to test our creativity by creating a game only using CSS and HTML.

We originally wanted to make a rock, paper, scissors game, but since that would've required some amount of JavaScript to function properly, we scrapped the idea fairly early on. We instead settled on making a variation of the NES game "Duck Hunt". This is a game concept that works just fine with no scripting – the only required interaction is clicking entities on the screen, which can be achieved by styling HTML checkboxes. The primary constraint for the assignment was that we had to use minimal, if any, JavaScript.

A personal project I made to explore, test, and practice PHP. The site has two main sub-pages: the "regular" and "cursed" game pages. Both sub-pages let you simulate snakes & ladders games. You can choose both the number of players and dice, and the simulator will reflect the settings. The regular game operates with normal snakes & ladders rules, whereas the cursed variant adds additional rules to drastically affect how long games take to complete. The site also stores the settings and results of played games in separate sub-pages for each game type.

The process I used to develop the page was simply to find a feature to focus on, and use my current PHP knowledge to implement it as best I could. While the project did use CSS, I only did very minimal styling, and mostly to explore how CSS and PHP interact. By mostly neglecting styling in this way, I could focus entirely on the PHP code itself.

LAiLA is our bachelor's thesis. The original project came from NTNU's Department of Design, and was fairly open. Through working on the project, we ended up with a much narrower focus than the original project. What we've ended up with is an AI-based system which uses generative artificial intelligence to support lecturers in processes tied to student-evaluation in student-dense programming courses.

Our project had a fairly standard development lifecycle, moving back and forth between different phases: establishing needs / requirements, designing, developing, and testing. The development process itself used an agile process, where we rapidly develop and test new features before merging them into our main Git repository.

My primary contributions to the project were tied to the backend development – such as server routes and controllers, and database planning, development and integration. Despite this backend focus, every team member – including myself – made contributions to both the frontend and backend.