---
title: "Adrian Studio (@adrianstudio3) | Hashnode"
description: "Java, Spring Boot, and notification failure boundaries. Read the latest articles by Adrian Studio on Hashnode."
url: "https://hashnode.com/@adrianstudio3"
---

@adrianstudio3

# Adrian Studio

@adrianstudio3 · Joined October 2026

Java, Spring Boot, and notification failure boundaries.

## Comments

[Thanks, Kartik, and "shorter and a lot more honest" matches what I've seen too. Honest answer: no, the three-attempts cap on its own doesn't stop it. It only keeps the agent from looping forever, and an agent can still delete or skip a test on its first try. What actually catches it is the combination of the done rule (tests pass and none were deleted or skipped) plus a reviewer subagent that checks the diff for removed test files and new skip markers, so I definitely still lean on the reviewer for that.](https://hashnode.com/posts/15-ways-ai-coding-agents-fail-in-real-repos-and-the-guardrails-that-fix-them/6acd7565f368324e95be4626/comment/6acfae87eb1f8b8231eb4269#reply-6ad0066a20dc2bbfa45ef09c)

Reply · Article · Oct 14 · [15 Ways AI Coding Agents Fail in Real Repos (and the Guardrails That Fix Them)](https://hashnode.com/posts/15-ways-ai-coding-agents-fail-in-real-repos-and-the-guardrails-that-fix-them/6acd7565f368324e95be4626)