↓ Skip to main content
Michael Hönnig
Michael Hönnig

Michael Hönnig

Senior software developer, backend focus
Java, Kotlin, Spring Boot, PostgreSQL, ReBAC, agentic-AI-assisted development

Software development and consulting
#

Until autumn 2027 I am only available for consulting engagements with a small number of hours – remote, in German and English.

My stack

Java / Kotlin / Spring Boot, PostgreSQL / pl/pgSQL, TypeScript / Angular. Current focus: ReBAC (relationship-based access control) and the use of agentic AI in software development – “vibe engineering”, i.e. AI-assisted software development with engineering discipline, as opposed to “vibe coding”.

How I work

It starts with a conversation to capture the domain, written down as BDD with Gherkin. Continuously gather fast feedback and incorporate it. During development XP / Kanban. Suitable tooling is built alongside to increase efficiency. Generated documentation is more correct and more current than hand-maintained documentation.

Get in touch Profile

Recent

Three Feedback Loops of Sustainable AI Software Development

·17 mins
AI Software-Development
Agentic AI can do more than develop new features: it can continuously improve the existing software. Three autonomous feedback loops show how this can work for correctness, performance and architecture, why the effort AI agents spend on changes could become a new maintainability metric, and why humans still have to set goals, limits and acceptable risks.

Agentic AI Is Like a Rocket: Identify the Target, Aim, Readjust

·13 mins
AI Software-Development
A guided rocket doesn’t have to be perfectly aligned at launch, as long as it knows its target and can correct its course. The same applies to AI agents: what moves to the center is the ability to aim at the right targets, check the direction automatically and readjust. Software development offers particularly good conditions for this.

Gray Software Factory: Autonomy by Risk, Not by Dogma

·7 mins
AI Software-Development
AI software factories come as light factories with a human in the loop and as dark factories without human reviews. A gray software factory works autonomously by default, but decides for every single change, based on an automated risk and quality classification, whether a human needs to be involved.

Topics