01
For organizations
Digital systems should create clarity, improve workflows and make technology investments measurably effective.
Personal Profile · Project Hub · Software Engineering
I combine software engineering, architecture, automation and governance so that digital systems don’t just work, but strengthen organizations, relieve teams and help people make better decisions.
Independent · expertly curated · in progress
Profile
I work on how modern IT landscapes can be evolved sustainably — from software development and platforms through automation to AI and agent systems that don’t just demonstrate, but reliably create value in everyday use.
I’m particularly interested in the connection between technical feasibility, organizational responsibility and practical operability. Good solutions, to me, emerge where architecture, development, security, governance and the user perspective come together — and where, in the end, better decisions, simpler workflows or tangible relief result.
A particular focus for me is AI-readiness: the question of whether IT services, platforms and architectures are designed so that AI systems can understand them, use them safely and evolve them in a controlled way. Because productive AI does not come from better models alone, but from systems that provide context, constrain actions, make decisions traceable and represent responsibility technically.
Development, review, quality, delivery and modern engineering processes.
AI and agent systems with context, boundaries, traceability and an operational perspective.
Structures, interfaces, platforms and decisions that remain sustainable over time.
Impact
AI, automation and architecture deliver their value not through novelty, but through impact: better decisions, more stable processes, relieved teams and systems you can trust in operation.
01
Digital systems should create clarity, improve workflows and make technology investments measurably effective.
02
Good tools reduce friction, improve quality and help people focus on the work that truly matters.
03
Technology should make things clearer, more reliable and more helpful — not more complicated.
AI-Readiness
Many AI initiatives focus on tools, prompts and models. The decisive question is whether existing IT services are AI-operable: Can agent systems understand them? Are there safe interfaces? Is context available? Are decisions observable, constrained and auditable?
01
Services need clear interfaces, descriptions and contracts so that AI systems don’t guess, but understand and act in a structured way.
02
What an agent can technically do is not the same as what it may do. Permissions, approvals and limits must be executable, verifiable and traceable.
03
AI systems need current knowledge, evidence and feedback from operations — otherwise they remain assistants without a reliable basis.
Focus areas
01
How AI changes tools, reviews, tests, documentation and engineering processes.
02
From chatbot to acting system: context, tools, approvals, observability.
03
How existing IT landscapes become AI-ready without losing control or maintainability.
04
Sensible automation where it improves quality, speed or clarity.
05
Rules, responsibilities and control points for production systems.
06
Making complex technical topics understandable without oversimplifying them.
07
How IT services must be designed so that AI agents can understand, observe and use them in a controlled way — with machine-readable interfaces, context, governance and an operational perspective.
Projects
Feasibility study · Demonstrator · AI-Readiness
Case studyA feasibility study on how IT services must be designed so that AI agent systems can support operation, optimization and further development autonomously and in a controlled way.
Impact
Shows that AI-readiness is not just an organizational or tooling topic, but an architecture and operations question for modern IT systems.
Knowledge & architecture project
activeAn independent project about reliable enterprise AI, agentic systems, architecture, governance and production-ready AI in real IT landscapes.
Impact
Guidance for reliable enterprise AI beyond hype and demos.
Data & media project
activeAn editorial weather almanac for Hesse — generated automatically every day from weather, climate and water-level data, with maps, audio and a data-driven pipeline.
Impact
Weather, climate and water-level data become understandable, regularly usable information.
Personal hub
MVP in progressThe central entry point for profile, projects, thoughts and references to further work.
Impact
A central entry point that visibly connects topics, projects and professional perspective.
Placeholder
plannedFurther websites, GitHub projects, articles, experiments or internal demos can be added here later.
Impact
Room for experiments that make technology tangible and assessable in practice.
Approach
Technology is not an end in itself. What matters is which problem gets solved, who benefits, and how impact becomes visible in everyday use.
Good architecture makes dependencies, boundaries and consequences visible.
A prototype is built quickly. AI becomes valuable in production only when services are understandable, controllable, observable and governance-ready — and when it’s clear what value they create in operation.
Complex topics should stay accessible without losing technical substance.
Logbook
Contact
I’m happy to exchange ideas on software engineering, enterprise AI, architecture and automation — especially where technology should turn into concrete value for organizations, teams or people.