<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Monoliths on Advancing Engineering</title><link>https://www.advancingengineering.dev/tags/monoliths/</link><description>Recent content in Monoliths on Advancing Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 29 Jun 2026 09:33:30 +0100</lastBuildDate><atom:link href="https://www.advancingengineering.dev/tags/monoliths/index.xml" rel="self" type="application/rss+xml"/><item><title>Best Tools for the Job in Agentic Development</title><link>https://www.advancingengineering.dev/posts/2026-06-best-tools-for-the-job-in-agentic-developement/</link><pubDate>Sun, 28 Jun 2026 20:27:40 +0100</pubDate><guid>https://www.advancingengineering.dev/posts/2026-06-best-tools-for-the-job-in-agentic-developement/</guid><description>&lt;p&gt;Agentic development changes what &amp;ldquo;good architecture&amp;rdquo; looks like. When implementation throughput is no longer the bottleneck,
the old reflex to split everything into tiny services can add more drag than value.
The better default for many teams is a slightly larger, cohesive deployable unit built with the best tools for each layer.&lt;/p&gt;</description></item></channel></rss>