My homepage as a development project

This homepage should do more than list roles and certifications. Within a few minutes, it should explain how I work, what I take ownership of, and where my hands-on development experience comes from. That makes the page a small product with an audience, information architecture, and a quality bar.

The key requirement is therefore not to show as much content as possible. Recruiters, clients, and colleagues should get a reliable picture quickly and be able to go deeper when they are interested. That creates a clear hierarchy: positioning, experience, own products, projects, and working approach.

I have been developing the page with Codex and Claude Code since 2026. The agents do not simply produce code without direction. I provide context, make product and design decisions, review suggestions, and choose the next useful step. It feels closer to working with a fast development team than to writing a single prompt.

That iterative approach is especially useful for a homepage: a new piece of information can change the order, call for a new component, or reveal a better way to phrase something. Changes become visible in the real layout and can be evaluated against the page itself.

My background in requirements engineering and quality assurance remains central to that work. For every new piece of content, I ask who it helps, whether the statement is clear, and whether it reflects real experience. I then check the interaction, responsive behavior, and important states with automated checks.

That is also how the new experience workflow came about. It does not merely claim that I build software. It connects understanding, building, and verification as one process. The page therefore tells the same story through its content and through the way it is built.

The homepage is an ongoing development project and deliberately remains in motion. New projects, lessons, and skills will be added when they make a real contribution to my profile. The important part is that the page should not only claim that I connect requirements, development, and quality. It should let visitors experience that connection directly.