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: 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.

About: A Node.js-based recipe search tool where users can filter by ingredients, cuisines or dietary needs, and save recipes as PDFs or send them via email.

Details:

• Purpose: Build a Node.js application that solves a real problem while integrating external packages in a meaningful way.
• Approach: I was responsible for the server setup, routing structure, project file organization, consistent error handling, and the PDF export feature using PDFKit. At the same time, my work needed to integrate seamlessly with the modules developed by my collaborator, which made the boundaries between our parts especially important. This gave me a clear technical focus, but also practical experience in building modules that function well within a shared system and balancing individual ownership with the needs of the team.
• Learnings: Server architecture and routing structure, error handling and input validation, external npm packages such as PDFKit and collaboration.
• Responsibility: I set up the server, structured the routing logic and implemented PDF generation using PDFKit.
• Feedback: Prasied for clear structure, strong error handling and effective use of external packages.
• Improvements: A future iteration could include user accounts for saving favorite recipes and automatic unit conversion for ingredients.