Emilie Sengenbjerg

About: A fully playable web-based version of the game Dice 30, built as a personal project to explore game logics.

Details:

• Purpose: Deepen my understanding of PHP, game logic and state management by building a complete game from scratch.
• Approach: I broke the game down into clear, isolated components: dice generation, locking mechanics, scoring rules, and most importantly the different phases of each round. A central challenge was separating the actions that happen within a round — such as re-rolling the remaining dice — from the state that marks the end of a round. At that point the game needed to calculate the total, determine whether the player reached 30, apply any penalties, reset round-specific values, and increment the round counter. By modelling the game as distinct phases, I avoided tangled logic and created a predictable flow. I also added persistence with SQLite, a dynamic score calculator, and a high-score list. After the complexity of Yrgopelag, Dice30 became a focused exercise in building clean, testable logic without relying on frameworks.
• Learnings: Structuring game logic, state handling and score calculations, data storage & planning and executing an independent project.
• Improvements: Accessibility and UX refinements would enhance the overall experience. Fortsatt development of multi-player mode.

About: A fullstack quiz application built with a C#/.NET backend, Docker setup and a DevOps pipeline for deployment, together with a React frontend. I was responsible for backend architecture, API design and all DevOps work, while my project partner focused on the game page and client-side score handling.

Details:

• Purpose: Create a C#/.NET project that demonstrated object-oriented structure, API design and practical backend development. Instead of building a console-based game as suggested in the assignment, we wanted to explore how a C# backend could be combined with a modern web interface and deployed as a fullstack application.
• Approach: We built a C#/.NET backend with models, services and a web API that handled the quiz logic, highscore and data flow. To make the project accessible on the web rather than only in a console environment, we created a simple React frontend and connected it to the API. I set up Docker containers for both backend and frontend, wrote the Dockerfile, and configured a simple DevOps pipeline to build and deploy the application. This allowed us to package the system consistently and deploy it as a unified fullstack project.
• Learnings: Practical experience with C#/.NET structure, API design, first experience of Docker and Dockerfile creation, container-based deployment, and how to connect a typed backend with a modern React interface. I also gained a great understanding of DevOps workflows and how backend and frontend actually interact in a deployed environment.
• Feedback: Praised for taking the assignment beyond a console application and instead building a fullstack solution with great structure, working API endpoints and a functional deployment pipeline.
• Improvements: Adding persistent storage, expanding the quiz logic with difficulty levels, and exploring faster hosting options to reduce container cold-start delays and improve overall UX.

About: An interactive booking application for the fictional island resort, built in a playful Super Mario-universe.

Details:

• Purpose: Develop a complete hotel booking system using PHP, SQL and the Central Bank API, including hotel registration, booking flow with transfer codes, database storage and required feature sets.
• Approach: I approached the project as a small business system rather than a school assignment. I built an admin flow where administrators could create accounts with hashed passwords, log in, and change their credentials. All admins shared the same permission level, but I added an extra security layer: a master code stored in .env, required for actions involving admin operations and financial decisions. The goal was to reduce two realistic risks — hashed passwords being cracked in a database breach, and an admin leaving an active session open.
  I also focused heavily on dynamic UX: prices and discounts were presented based on live data from the database, and I built a dynamic total-price calculator that considered the selected service, date (number of hotel nights), and applicable discount logic. The clickable availability calendar was fully synchronized with the booking form. The project sparked my interest in system design, security, and building robust admin workflows with many moving parts.
• Learnings: Complexity management, API integration and data validation, database design and dynamic rendering, security and structuring larger codebases.
• Feedback: Recognized for strong structure, dynamic implementation and solid database design.
• Improvements: An expanded admin dashboard with room management, discount controls and occupancy insights would strengthen the system.