Posts

Featured in the school news, and a look back at the elective.

MCP could connect an assistant to our event workflow. For now, we’re finishing the application.

The first time Johan and Lise saw their workflow in our application.

Protecting our credentials, and deciding what happens to Engestofte’s data.

Two developers, several tickets, and the communication that keeps them aligned.

Turning Johan’s workflow into a project we can build together.

Listening to the business before deciding what to build.

Why the document isn’t the asset.

Building it, then not trusting it.

Designing an AI grader before writing any of it.

A chatbot that never goes stale.

What happened the first time I built one.

What got built, and what I’d change.

Four levels of state, one weekly menu editor.

When the groundwork finally paid off.

Two roles, shared components, one feature.

Routing, JWT auth, and edge cases real users find.

Refactoring my way out of folder chaos.

Planning before writing a single component.

Aligning the docs with the real codebase.

From localhost to a real deployment.

Real JWT authentication, the hard way.

Integration tests and real-time WebSocket notifications.

Wiring controllers, routes, and dependency injection.

Where business logic actually belongs.

Integrating DeepL and Gemini AI.

A bug that silently ate my menu slots.

Understanding kitchens before writing any code.

The tool I always wished existed.