Need Human Support?
These are the common classics. If your question isn't covered, don't hesitate to reach out via email or LinkedIn. You can also dive deeper into my work by checking my GitHub repositories. All links are available below.
Frequently Asked Questions Let’s light things up.
Professional Experience
Since 2015
Specialized
Vue and Nuxt
Performance
& Accessibility
Programming skills
Here’s a snapshot of the technologies, tools and approaches I bring to every project - hand-picked to build performant, maintainable and accessible Vue-powered experiences.
-
Core Skills: JavaScript, TypeScript, HTML, CSS, Vue, Nuxt, Git
-
Long time no see: React, PHP, Firebase, Gulp, jQuery,
-
Other Tools & Technologies: Node, Vue-Router, Vuex, Pinia, Tailwind CSS, Sass/Scss, Pug, Storybook, Histoire
-
Build & Automation: WebPack, Vite, npm/yarn, pnpm
-
CMS & Backend: WordPress, FirstSpirit (FSXA-API), Storyblok
-
DevOps & Collaboration: Git (GitHub, GitLab, BitBucket), Asana, Jira, Confluence, Figma, Adobe XD, MS Teams, Slack
-
Testing & QA: Unit Testing (Vitest, Jest), Regression Testing, Lost-Pixel, Chromatic, Percy, Apple Voiceover
-
Methodologies: Accessibility, Atomic Design, BEM, Mobile-First & Responsive Design, Headless CMS, Agile/SCRUM
-
Spoken Languages: German (native), English
-
Soft Skills: I am a creative, organized, open minded, objective, autonomous, helpful & reliable team player
This toolkit reflects my skills even if there are many smaller libraries and stuff like Charts.js, day.js, Postman, several IDEs and stuff that is so basic that I don’t mention it within the following list.
Above all, I think the ideal technology stack must align with a project’s requirements - that said and left aside: since starting my career as a freelancer, I've lived and breathed Vue - working nearby daily with Vue 2 & 3 (Class Style, Options, and Composition APIs) and Nuxt 2 & 3 for full-stack projects.
I deeply appreciate everything the Vue ecosystem has brought to the table. For my very own website, I chose Nuxt 4 (for future-proofing) in SSR mode, Pinia for state management, Vitest for unit testing, and Histoire with Lost Pixel for documentation and visual regression testing. (While I typically prefer Storybook + Chromatic, Histoire's out-of-the-box functionality and Lost Pixel's open-source/free model made them worth exploring - both are young tools with promising development potential.)
For styling, I used Tailwind 4. While I still love developing smart Sass functions and mixins for efficient styling, I acknowledge Tailwind's faster implementation. For content management, Storyblok proved excellent - though many solutions offer comparable quality with different pros/cons - and its application/content separation perfectly complements my tech stack. I also implemented a Redis caching layer: a fast in-memory solution with a sufficient free tier and helpful tools like Redis Insights.
I use GitHub for version control, ESLint with custom rules to maintain code quality standards, and Husky for Git hooks to ensure repository integrity.
What I really like about Vue is its true component-centric separation of concerns. Unlike Angular’s “horizontal” approach — splitting HTML, JavaScript and CSS into separate files — or React’s tendency to blur markup, logic and styles together, Vue’s Single-File Components bundle each component’s template, logic and styles in one place. This “vertical” separation keeps everything related to a UI unit encapsulated, modular and easy to maintain — without hunting through multiple folders or wrestling with global namespace collisions.
And then there is Nuxt, which takes Vue even to the next level: out of the box one gets server-side rendering (SSR), static site generation (SSG), powerful routing, based on vue router, which can be file-based or completely dynamic, automatic code splitting and optimized builds. In short, Nuxt not only accelerates development but also enforces best practices by integrating the full web stack into one coherent, Vue-powered meta-framework.
Also I love Vue's rich ecosystem providing really cool solutions for every problem - Pinia
, VueUse
, Vitepress
, VueDevtools
, Histoire
, Nuxt
, and many more are simply working out of the box using them in Vue. Also the Vue community is providing many framework agnostic solutions like Vite
, Vitest
and Oxc
- reshaping how developers of every framework build, test and optimize their applications. I’m constantly impressed by the elegance and performance of these tools (even if nothing in this world is perfect of course), and I believe in supporting the people behind them, because their innovations lift the entire front-end world.
Accessibility isn't just a social responsibility; it's a fundamental aspect of building a high-quality application. By prioritizing it, we ensure a better user experience for everyone—from those with permanent disabilities to users with temporary limitations like a broken arm or a poor internet connection. This inclusive approach not only reflects a commitment to all potential users but also expands our market reach and ultimately enhances the overall usability for every user.
My approach to accessibility is comprehensive and professional. I follow W3C best practices to meet specific compliance levels (A, AA, or AAA), collaborating closely with UX/UI designers from the earliest stages of development. This ensures that accessibility is integrated into the core concept of an application, aligning with both user needs and technical requirements.
To maintain a high standard of quality, I use a combination of automated and manual testing. I regularly test with screen readers and other assistive technologies to catch issues that automated tools might miss.
Additionally, I utilize monitoring tools to proactively identify and resolve any accessibility issues as early as possible in the development lifecycle, well before deployment. This proactive approach minimizes rework and ensures the final product is a top-tier, accessible application.Wanna now more, read my article about Web Accessibility in 2025 European Accessibility Act, Modern Testing Tools, and Strategic Implementation.
Projects & Expertise
It actually began back in 2007, when I got my first Internet connection and was instantly blown away by the possibilities of the World Wide Web. With zero clue on how it all worked, I quickly taught myself to build rudimentary websites - and before long I was creating my own small affiliate projects and tinkering with private WordPress sites using HTML, CSS, and PHP in my spare time.
But the real dive happened while studying Socioeconomics at Uni Hamburg, and startet working at Surf Media GmbH, where I joined as a marketing working student in the marketing department of the company, and soon found myself filling gaps on the dev team. A manpower crunch meant I rolled up my sleeves and started turning landing-page concepts into live campaigns—designing, coding, and even handling full-stack tasks.
What began with responsive frontends in jQuery and taming SCSS to style chaos into order quickly revealed a deeper thrill: I loved not just sketching wireframes, but architecting the code that brought them to life. Over time, the technical side completely won me over - since then I’ve followed that spark into the JavaScript world and especially the Vue ecosystem, which I still love today.
I’ve documented a deep-dive case study on my work with a German energy provider, where I built a high-performance website using FirstSpirit as a headless CMS in combination with Nuxt, going into unit testing, visual regression testing, caching, and so on - beyond the technical stuff, I also cover how we streamlined team processes.
I do a nuxt starter
, and an Obsidian Theme
which are both kind of successful(!?). Also I did some other smaller projects like the vue capacitor starter
- which unfortunately nobody really cared about yet. ^^
If you’re hungry for more, my blog is packed with proof-of-concept write-ups and in-depth articles on everything from advanced Vue patterns to tooling deep dives. Feel free to explore and let me know which topics spark your interest!
Absolutely. I love jumping into brown- and green-field projects - whether it’s running discovery workshops to align on business goals, drafting interactive prototypes in, or defining a clear MVP scope. Together, we’ll map out user journeys, break features into prioritized backlogs, and validate technical feasibility before a single line of production code is written. This upfront collaboration ensures we hit the ground running, mitigate risks early, and set realistic expectations for timeline and budget.
I thrive in interdisciplinary environments, collaborating seamlessly with developers, designers, marketers and product owners. By bringing my Vue/Nuxt expertise to Scrum ceremonies—from sprint planning and backlog grooming to daily stand-ups and retrospectives—I ensure that complex tasks are tackled efficiently and that everyone stays aligned. My goal is always to amplify the team’s strengths, streamline decision-making and deliver cohesive, high-impact solutions.
Since kicking off my freelance journey in 2015, I’ve successfully delivered 10 full‑lifecycle projects, each spanning discovery, development, launch, and post‑launch refinement. These engagements range from large‑scale Vue/Nuxt migrations for enterprise clients like RheinEnergie to greenfield prototypes, headless CMS integrations, and performance‑first B2B dashboards. On my LinkedIn profile, you’ll find highlights of these projects—including metrics such as a 40 % reduction in Time‑to‑Interactive for a major energy portal and seamless integrations with FirstSpirit and Storyblok—underscoring both the technical depth and business impact of my work. Feel free to explore the detailed case studies on my blog for an inside look at tools used, architectural choices made, and lessons learned along the way.
Mission & Philosophy
In my view, the big challenge in web development is not the short-term provision of complex features, but rather the ability to guarantee this in growing environments over the long term.
The basis for this is a well-structured code base and clean architecture as a foundation, as well as the consistent use of patterns and good test coverage. By adhering to these three basic principles, it is not only possible to potentially reduce complexity and ensure low error rates and stable performance, but also to implement a highly scalable and maintainable application. Underlying this, I rely on adherence to common QA processes, code reviews to share knowledge and ensure quality, and adherence to established patterns and principles (such as DRY, SOLID) that make code predictable and robust. In my view, it is important to cultivate an awareness and spirit of ambition and discipline within the team.
Another building block, in my opinion, is documentation that is as clean as possible, in order to make it easier for new team members to get started and to enable quality criteria to be maintained. It's not about green marketing, but about technical durability and low life cycle costs.
A good product is the result of teamwork—that's why I value interdisciplinarity. My academic background is based on the teachings of social economics, which attempts to shed light on problems from a business, legal, economic, and sociological perspective. Often, different solutions to problems can be identified from the various perspectives and toolkits. During my studies I've learned that it makes sense to approach problems with a broader horizon, in order to develop truly good solutions ensuring solving a problem by involving technical, monetary, visual and last but not least the users perspective.
A brilliant developer working in isolation may well solve a technical problem, but open collaboration – through transparent communication, shared knowledge, and the active inclusion of all perspectives – ensures that we ultimately solve the right problem and that the solution can be optimally tailored to all stakeholders (users, business, development). From my perspective as a developer.
I consider it essential to advise, identify problems and opportunities, and engage in constructive discourse with stakeholders from other disciplines in order to bring my arguments to bear and enable product managers to make the right decision.
Navigating the inherent tension between quality and time-to-market is a core challenge in software development. My philosophy is that the fastest path to a durable solution is through clean, sustainable code. While I recognize that critical issues like bugs or urgent legal mandates demand immediate action, building a complex application is a marathon, not a sprint. Rushing leads to technical debt, which slows us down significantly in the long run.
I focus on delivering high-quality, maintainable, and scalable solutions efficiently. My approach isn't about over-engineering; it's about being pragmatic. I prioritize spending the time necessary to build the application correctly from the start. This proactive mindset minimizes future rework and ensures the product remains adaptable to new requirements, ultimately accelerating our development velocity over time.
In general I would say I run pretty fast! ; )
The conviction that great software can empower people and improve their everyday lives. Whether it's a seamless user experience, a barrier-free interface, or a stable application that reliably does its job in the background—I want to build things that make a real, positive difference.
The code itself is the tool, not the purpose—interdisciplinary teamwork, insight into different schools of thought, and the associated harmonization of constructive arguments and perspectives to create the best possible software that empowers people to improve their everyday lives is a major motivator for me.
Workflow & Collaboration
I thrive in interdisciplinary environments, collaborating seamlessly with developers, designers, marketers and product owners. By bringing my Vue/Nuxt expertise to Scrum ceremonies—from sprint planning and backlog grooming to daily stand-ups and retrospectives—I ensure that complex tasks are tackled efficiently and that everyone stays aligned. My goal is always to amplify the team’s strengths, streamline decision-making and deliver cohesive, high-impact solutions.
Quality and punctuality are cornerstones of my process. I break every project into clear milestones, conduct regular demos and code reviews, and leverage automated testing (unit, integration and regression suites) to catch issues early. Transparent communication—daily standups or weekly check-ins—ensures we stay aligned, so you always know where we stand and can provide feedback before it’s too late.
Flexibility and clear communication are at the core of my process. While I plan meticulously to keep timelines on track, I understand that requirements can shift or new feedback can emerge. In general, I welcome constructive criticism and engage in open discussions to realign on priorities. My goal is always to turn change requests into opportunities for improvement — optimizing processes, refining solutions, and ensuring we stay focused on your business objectives.
In every agile engagement, I integrate deeply into the full suite of Scrum rituals to keep teams aligned, remove blockers, and continuously improve our process:
- 1. Sprint Planning: As part of sprint planning, I collaborate with the Product Owner to break down high‑level requirements into clear, achievable user stories. Drawing on my Vue/Nuxt expertise, I help estimate effort, flag technical risks early, and propose sensible acceptance criteria to ensure the development team has everything it needs to start the sprint with confidence.
- 2. Daily Stand‑ups: Each morning, I join the daily stand‑up to share progress, surface any roadblocks, and coordinate with UX designers, QA engineers, and backend developers. My goal in these quick syncs is to keep momentum high—if I hit a blocker, I’m proactive about pairing up or escalating to the Scrum Master so the rest of the team can continue unhindered.
- 3. Backlog Refinement: In backlog refinement sessions, I review upcoming user stories with the team, offer technical insights (e.g., component architecture, state‑management strategies), and help split large epics into manageable tasks. This continuous grooming ensures our backlog remains prioritized, well understood, and realistically sized for future sprints.
- 4. Sprint Reviews: At the end of each sprint, I demo completed features to stakeholders—whether that’s marketing, product management, or external partners. I focus on demonstrating real usage flows, collecting immediate feedback, and capturing any change requests as new user stories. This transparency builds stakeholder trust and keeps the product roadmap aligned with business goals.
- 5. Sprint Retrospectives:In retrospectives, I facilitate or contribute to honest discussions about what went well, what didn’t, and how we can improve. Leveraging techniques like “Start/Stop/Continue” or “5 Whys,” I help the team identify actionable improvements—whether that’s refining our linting rules, adjusting our CI pipeline, or tweaking our definition of done.
Across all these ceremonies, I wear multiple hats—contributor, technical advisor, and occasional facilitator—always striving to keep the team’s workflow smooth, the codebase healthy, and the product evolving in line with stakeholder expectations.
Absolutely. I stay involved as long as you need me—even after launch. For minor tweaks or bug fixes, you can simply book additional maintenance hours. For larger ongoing engagements, I’m available based on my capacity and your roadmap. This ensures your application remains up to date, secure, and performant over time.
Yes—professionalism and confidentiality are a given. I’m happy to sign NDAs or full contracts before starting any project. You can trust that your intellectual property stays protected every step of the way.
I rely on a carefully curated set of hardware to ensure smooth, high-performance workflows across platforms:
-
Primary Laptop: MacBook Pro M3 Max (Apple Mac OS) – blazing speed for intensive front-end builds, native Safari testing and seamless Nuxt deployments.
-
Secondary Laptop: Legion Pro 7i Gen 10 (Intel, Windows/Linux) – flexible dual-OS setup for cross-platform debugging and Windows-specific performance checks.
-
Test Devices: iPhone 12 Pro , Motorola Moto One and Apple iPad 11 – real-world mobile and tablet QA.
-
-
-
Keyboard: Logitech MX Keys S – tactile, backlit typing for marathon coding sessions without to loud click noise.
-
-
-
-
-
This setup lets me prototype, code and test with professional-grade tools that cover every stage of modern web development.
Rates, Workflow & Availability
I charge 100,- Euro per hour for remote work. For onsite engagements, I either bill travel time and expenses separately or offer a flat monthly fee that covers commuting and workspace rental - depending on your location. Feel free to ask for a custom quote based on your site; I’m based in Cologne and happy to provide detailed rates for your specific need.
I’m always reachable via LinkedIn
or
email and can adapt to a variety of commitments - from part-time support or short side-projects to full-time engagements. Whether you need a few hours a week or a dedicated developer on your team, let’s discuss what works best for your timeline and goals.
Based in Cologne, Germany I am available for onsite and/or remote work (of course providing my own working place and hardware setup, also using MacOS, Windows or Linux). I am also available for engagements throughout Germany, Switzerland, Austria, and am open to considering projects in other EU countries.
Early in my freelance career, I focused on shorter engagements (3–6 months) to broaden my experience, see how different companies handle several situations. Today, I welcome longer-term partnerships, while still fitting in smaller projects for existing clients. New projects typically require a minimum commitment of two weeks to establish momentum. I’ve thrived in compact teams of 3 developers as well as interdisciplinary squads of 15+ members. My sweet spot is Scrum teams up to 10 people—large enough for rich collaboration, small enough for rapid decision‑making.
Clients, Partners & Community Projects
I am proud to present the organisations with which I have partnered during my career, along with the open-source projects I have created and still continue to maintain. Real-world collaborations and community-driven code, all under one roof.
RheinEnergie
Agital-Online / esyoil
IU Internationale Hochschule (formerly IUBH)
Logic Joe
Guide 2
CFO Management
KRAVT / Katjes
Lions Club Hamburg
Traffic Partner
Austin Frasier
Workgenius
Progressive