↓ Skip to main content
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

How I Write Blog Articles with AI

·9 mins
Below my articles it says that they were written with AI assistance. Here I describe what that means in practice: from the idea on a forest walk through the expert discussion with ChatGPT to draft, review, diagrams, translation, preview and X post with skills in Claude Code – and which part remains mine.

Not Unit Tests, but Our Units Are the Problem

·15 mins
Since coding agents produce huge numbers of fine-grained tests, some demand that we give up unit tests. But the problem is not unit tests, it is units that are defined too small: tests that lock in the current class structure make refactoring harder despite high coverage and a high mutation score. As a measure of refactoring safety, both metrics are incomplete without the tested module depth. The article proposes testing domain components through their public API, determining a module-related mutation score and defining test boundaries as part of the architecture.

Self-Test: How Trunk-Based Is My Workflow?

·7 mins
My idea of trunk-based development was naive: every commit straight to main, branches frowned upon. Research showed that short-lived branches with review are the norm and release branches are explicitly provided for. This self-test asks twenty questions about what actually happens in a team’s daily work and rates, following trunkbaseddevelopment.com, how far the practices of trunk-based development are in place: branch lifetime, integration, reviews, unfinished features, CI, local build, red trunk, code freeze, code ownership, story size and release readiness. The result is a degree of adoption with hints at possible bottlenecks, not a grade; questions and weighting reflect my current state of research.

Three Feedback Loops of Sustainable AI Software Development

·17 mins
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
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.

Topics