The Age of ReDevTest: Why Requirements Matter More Than Code

For many years, software development was code-centric. We wrote requirements, then quickly moved to implementation. Tests helped, but code was the real source of truth. AI changes this completely.

Why System Use Cases Are Perfect in the Age of AI

AI is changing how we build software. Code, tests, and even UI can be generated very fast. This is powerful, but it also exposes a big weakness in many projects. AI does not understand intent by itself. AI only works well if the input is precise. That is why system use cases are more relevant than ever.

Why Most AI Productivity Gains Are Invisible and How AIUP Changes That

AI is everywhere in software development. Many teams already use AI code assistants daily, and the promises are big: faster development, higher productivity, fewer developers needed. Gartner even talks about potential productivity gains of 25–30% across the software development life cycle.

AI4RE Meets AIUP: Why the IREB Micro-Credential Fits Perfectly

Recently, the AI4RE micro-credential was introduced by International Requirements Engineering Board (IREB). At first glance, it may look like just another certification topic around artificial intelligence. When you look closer, however, it becomes clear that AI4RE fits extremely well with the AI Unified Process (AIUP).

Stop Starting with Code: Start with System Use Cases

When I work with AI Unified Process, the focus is always on system use cases. They are the core artifact that connects requirements, existing systems, and generated implementation. This is not big upfront design. It is iterative and incremental. One use case at a time.

Testing Emails in Spring Boot with Testcontainers and Mailpit

Testing email functionality is often painful. SMTP servers are external, tests become slow or flaky, and local setups differ from CI environments. As a result, many teams either mock the mail sender or skip proper email tests completely.

One Query, Complete Object Graphs: Nested DTOs with jOOQ MULTISET

In my previous post about Open Session in View, I explored how this default Spring Boot setting can hide serious performance problems. The N+1 query problem sits behind a system that looks correct in development, but breaks down under real production load. Suddenly, you see 701 queries where 1 would be enough. Today, I want [...]

The Hidden Performance Killer: Understanding Open Session in View in Spring Boot

If you’ve ever wondered why your Spring Boot application feels sluggish under load despite appearing to work perfectly during development, there’s a good chance you’ve encountered the Open Session in View (OSIV) anti-pattern without even knowing it.

An AI-Ready Architecture for Business Applications

Agentic AI is changing how we build software. AI is no longer just a helper that writes small code snippets. It can reason about requirements, generate larger parts of a system, validate behavior, and keep code consistent over time.

Spec-driven Development is not Task-driven AI

Spec-driven development is suddenly everywhere. Many AI tools claim to support it, and many teams say they are already doing it. But when I look closer, what I often see is something very different. The typical flow looks like this: requirements -> plan -> tasks The requirements are quickly translated into a plan, and the [...]

Why User Stories Are a Poor Fit for Spec-Driven Development

User stories are popular in agile teams. They are short, readable, and focused on user value. For many teams, they help with planning and coordination. However, when the goal is Spec-driven Development, user stories show serious limitations. They push teams to create plans and task lists before the real requirements are clear. This makes them a [...]

The Human Perspective: Why “Empower the Team” is a Definition of Success in 2025

The fifth chapter, Empower the Team, is arguably the linchpin upon which all the other Lean principles depend. In the conclusion of my previous exploration of rapid delivery, I noted that a team’s speed is not achieved by working harder, but by systematically designing a process for the team that flows. But who designs that [...]