INNOQ Technology Night (Köln): Big-Data-Architekturen und Datenprodukte 👉 21 May 18:30

Blog & Articles

Die 1%-Methode für Code und Architektur: Modernisierung als Gewohnheit

„Wir wollen ja modernisieren, aber das Tagesgeschäft kommt immer dazwischen." Diesen Satz höre ich in Kundengesprächen jede Woche. Das Problem ist nicht der Wille, sondern die Vorstellung, dass Modernisierung ein Projekt sei. In diesem Beitrag zeige ich, warum kontinuierliche Modernisierung als tägliche Team-Gewohnheit funktioniert, wo individuelle Vorsätze scheitern und wie zehn Minuten am Tag über Monate eine Architektur entstehen lassen, die ein Big-Bang-Projekt nie hinbekäme.

Using the space, not optimizing the treadmill

Features per unit of time is not a meaningful metric. What counts is whether they satisfy a real user need and contribute to a desired outcome. Agentic development opens up the space to finally take that seriously.

The Missing Half of Your Data Strategy

Why Data Literacy Makes or Breaks Data Product Oriented Architectures

Nebu: Self-made sovereignty

There are plenty of open-source alternatives to Slack. None of them deliver real sovereignty. Community editions are deliberately pared down so no company can run them in production, while enterprise features sit behind commercial licenses. This article shows why “building it yourself” is no longer a utopian idea today, but a realistic option for anyone with a product vision and a bit of DIY courage.

Accidental Complexity in the Heart of Software

Domain-Driven Design went mainstream over the last ten years – in parallel with a wave of digitalization and modernization projects. That is not a coincidence. And it explains a lot about why so many of these projects fail to deliver what they promise.

Hail Mary: Why domain knowledge cannot be extracted from experts

Developing with AI through the cognitive Lens

From Vibe Coder to Agentic Engineer

I no longer read every line of code that’s produced in my projects. I think most people who work intensively with AI agents feel the same way. When an agent produces a thousand lines in ten minutes, line-by-line review is no longer realistic. At the same time, that code ends up in production, and someone has to take responsibility for it.

The Right Kind of Hard

More structure, more output, more exhaustion. Spec-driven development has helped me get better results from AI agents – and drained my energy in the process. About dead weight, false clarity, and hidden costs I didn’t plan for.

AI Features for Jira Data Center – No Atlassian Cloud Required

Our Digital Independence Day recipe for going off-cloud

Where AI Helps (and Hurts) Across Different Coding Scenarios

Where does LLM-assisted software development improve developer productivity—and where does it fall short? Instead of treating AI in software development as a one-dimensional productivity booster, we explore the question across several dimensions suggested by a Stanford-adjacent study: project maturity, task complexity, and the popularity of the programming language. The goal is to create a more realistic expectation baseline for both software developers and leaders—well away from today’s hype.

Spec-Driven Architecture: When Agents Build, Architecture Must Speak

Spec-Driven Development gives agents a clear foundation for implementation. What it doesn’t solve is how a portfolio of systems stays coherent. Spec-Driven Architecture applies the same principle at the architecture level, using contracts as versioned boundaries and guarantees—enforceable in agentic workflows and in the CI/CD pipeline.

REST Beats MCP

How AI agents actually benefit from hypermedia

Spec-Driven Development is Domain-Driven Design’s Impatient Cousin

Spec-driven development tools like BMAD promise to fix the requirements bottleneck that agentic development teams face. But is it actually a good fit for your organisation?

The right size of a Data Product

Setting the boundaries of data products incorrectly can lead to integration issues, unclear ownership and duplicated logic. This guide offers practical heuristics for creating data products of the right size.

Agents good in the end?

A story of unleashed productivity and mental load

Understanding AI Coding Patterns Through Cognitive Load Theory

AI coding assistants either severely harm learning or enhance it beyond manual coding—depending entirely on interaction patterns. A recent study reveals six distinct patterns with dramatically different outcomes. We’ll examine why through cognitive psychology and explore the study’s limitations.

Ein Überblick der AI-assistierten Softwareentwicklung in 2026

Birgitta Boeckeler (ThoughtWorks), Heinrich Hartmann (Zalando) und Sven Johann haben sich über den aktuellen Status der AI-assisted Software Entwicklung unterhalten: was ist wirklich Wichtiges in 2025 passiert? Welche stabilen Muster können wir ableiten? Was gibt Orientierung und Einordnung? Und natürlich ein paar Einblicke in den Future of Software Engineering Retreat in Utah an dem Birgitta teilgenommen hat. Die Unterhaltung gibt es natürlich auch als Podcast. Dieser Artikel ist aber eine menschlich kuratierte Zusammenfassung.

Features für einen schnelleren JVM-Start

Class Data Sharing, Project Leyden, CraC und mehr

Neuland reloaded

When Angela Merkel said in 2013 that the internet is ‘Neuland’ (uncharted territory) for all of us, the amusement online was considerable. Viewed from some temporal and substantive distance, one can now recognize a perspective from which she was indeed correct.

From Vibe Coder to Code Owner

AI agents generate thousands of lines of code in no time. If you want to fully leverage their potential, you can no longer review every single line – but you’re still responsible for the software. How do you take ownership of code you haven’t fully read? The answer lies in the agent harness: a system of deterministic checks, AI reviews, and targeted human review that enforces quality instead of hoping for it.

I sandboxed my coding agents. Now I control their network.

Restricting network access for AI coding agents with a proxy allowlist

Jeder kann Architekt sein!

Und jede natürlich auch. In diesem Artikel zeige ich, dass die Architektenrolle andere Kompetenzen verlangt, als viele annehmen.

Your Database Table is an awful API

A shared database table can feel like the ultimate shortcut: no API design, no contracts - just a schema. The catch is that this convenience quietly turns into friction: it blurs boundaries, slows change, and makes independent evolution harder than it needs to be. This article looks at why tables (and data-model-shaped “generated APIs”) are such a tempting trap - and what better integration boundaries look like.

Let’s Not Normalize Insecure AI Assistants

How the Lethal Trifecta Makes Today’s AI Assistants Unsafe by Design

Die persönliche KI ist schon da

Drei Wochen mit OpenClaw auf einem Raspberry Pi und ein Blick darauf, was auf die Softwarearchitektur zukommt.