Server logic. Relational schemas. Deployed and holding.

Every architectural decision here is measured against one question: does it hold under real conditions? If it doesn't, the choice is wrong.

I studied UX-UI design and back-end development at Noroff School of Technology in Norway, which gives me a complete view of how digital products get built. I design interfaces based on how people actually use software, and I build the systems behind them — REST APIs, database schemas, deployments in JavaScript. Working across both sides means I design with technical constraints in mind and build with the end user in mind. I like solving problems where user needs and technology meet, and I bring both perspectives to every product I work on. I'm looking for a role where I can put this combination to work and deliver real impact from day one.

Close-up of a terminal window on a dark monitor, Node.js server log output scrolling — green and cyan text on near-black background, screen glow casting cool light on the surrounding desk surface, tight crop showing only the screen and immediate edge of the keyboard

— Constraint-Driven Design

The problem defines the stack.

REST endpoints are structured around the resource, not the framework's convention. Database schemas are normalized to the query pattern, not the ORM's preference.

Deployment targets are chosen for reliability and cost at the project's actual scale—not for what looks good on a resume. Constraints are the spec.

See the Projects

Actively building. Available now.

Production-grade projects are live and linked. Review the architecture, read the code, run the tests. That's the full picture.