<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Lombok on tsvinc</title>
		<link>https://tsvinc.dev/tags/lombok/</link>
		<description>Recent content in Lombok on tsvinc</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://tsvinc.dev/tags/lombok/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Build Was Green the Whole Time</title>
				<link>https://tsvinc.dev/posts/the-build-was-green-the-whole-time/</link>
				<pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/the-build-was-green-the-whole-time/</guid>
				<description>&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;12:06.&lt;/strong&gt; &lt;code&gt;irc-bot&lt;/code&gt;, freshly ported from Spring Boot to Micronaut 5.0.6, is committed with fourteen passing tests.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;13:35.&lt;/strong&gt; A test I had just written fails on a class name.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;13:56.&lt;/strong&gt; A sanitiser build of the group&#39;s C IRC daemon names the line where it writes to address zero.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;19:15.&lt;/strong&gt; The bot is launched against a real IRC network for the first time. By 19:20 there are three more failures on the list.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Five failures in one afternoon. None of them broke compilation, and none of them tripped a test that existed before I went looking. They turned up because something finally ran: a proxy check, a socket, a live launch.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Upgrade Errors That Named the Wrong Layer</title>
				<link>https://tsvinc.dev/posts/every-error-named-the-wrong-layer/</link>
				<pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/every-error-named-the-wrong-layer/</guid>
				<description>&lt;p&gt;A compiler error is supposed to work like an address. It names a file, a line and a symbol, and the fix lives somewhere near what it names.&lt;/p&gt;&#xA;&lt;p&gt;One morning in July, five Maven repos put that to the test. They had last been modernized in August 2025, and now all of them needed their frameworks dragged forward at once: Spring Boot 3.4.1 to 4.1.0 in two, Quarkus 3.17.4 to 3.37.4 in one, and two Micronaut projects from 3.x to 5.0.6. The JDK doing the compiling was Temurin 25.0.3. Every pom still targeted Java 17.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
