This page contains the specific devlog posts from my portfolio that I want to include in the exam. The goal is to show the development of my application over time, including what I built, what I learned, and the technical decisions I made along the way.
Also worth noting: the README in the repo has been updated over time to match the exam/hand-in requirements, and the longer technical rundowns in these posts are there for depth — not required reading.
Week 1 establishes the baseline: initial scope, core domain concepts, and early architectural decisions (entities, relationships, immutability/soft-delete direction).
Week 5 focuses on architecture refinement and testing strategy (ISP-driven interface design, RestAssured + Testcontainers integration tests, DTO mapper pattern).
Week 6 shows a “deployment-ready” step where I secured the API with JWT authentication and role-based authorization, and how that was integrated cleanly without breaking the existing structure/tests.
Devlog Week 6: JWT Authentication & Role-Based Authorization # This week was entirely dedicated to building a deployment-ready authentication and authorization system. No new domain features—just securing everything that already exists. The focus was on JWT tokens, role hierarchies, and integrating security seamlessly into the existing architecture without breaking tests or existing functionality.
Devlog Week 5: Interface Refinement, REST API Testing & The Mapper Pattern # This week marked a significant shift from building features to refining architecture and establishing a robust testing foundation. The focus was on three major areas: granular interface design following ISP principles, comprehensive REST API testing with RestAssured, and implementing the DTO mapper pattern.
Devlog Week 1: Project Kickoff & Scope # So, first of all, welcome to this first week post of the development of my little maintenance log. Just for posterity, let’s start with what is in my README for the project, since that actually breaks down what it is: