<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agentic Development on Professional developer</title><link>https://www.professionaldev.dev/series/agentic-development/</link><description>Recent content in Agentic Development on Professional developer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.professionaldev.dev/series/agentic-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Agentic Development: What Actually Works in Legacy Java</title><link>https://www.professionaldev.dev/post/agentic/intro/</link><pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.professionaldev.dev/post/agentic/intro/</guid><description>
&lt;p&gt;For six months I've been running coding agents on a real legacy codebase — Java 17, Spring Boot,
4,000+ files, multi-tenant SQL Server. Not toy problems: production bug fixes, SDLC-style
feature work, security remediation, performance regressions. The agents got better. I got better
at knowing what to let them do, and what to make them stop doing.&lt;/p&gt;
&lt;p&gt;This post opens a series on the handful of patterns that actually paid off.&lt;/p&gt;</description></item></channel></rss>