<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Insights on AereA GmbH — Software that still runs in five years</title>
		<link>https://www-main.uat.aerea.de/en/insights/</link>
		<description>Recent content in Insights on AereA GmbH — Software that still runs in five years</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
			<managingEditor>info@aerea.de (AereA GmbH)</managingEditor>
		
		
			<webMaster>info@aerea.de (AereA GmbH)</webMaster>
		
		
		
			<lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www-main.uat.aerea.de/en/insights/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>How we develop with AI agents — and the safeguards that turned out to be necessary</title>
				<link>https://www-main.uat.aerea.de/en/insights/ai-agent-review-pipeline/</link>
				<pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-main.uat.aerea.de/en/insights/ai-agent-review-pipeline/</guid>
				<description>&lt;p&gt;This text describes a pipeline that runs in production here — on a multi-tenant communication system built on ASP.NET Core, Angular and FreeSWITCH, with self-hosted GitLab. Every finding below comes from a real run and was found and fixed &lt;strong&gt;before the merge&lt;/strong&gt;. We do not name the system, because individual findings would otherwise be traceable back to it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;bottleneck&#34;&gt;What is the actual bottleneck in developing with AI?&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#bottleneck&#34;&#xA;     aria-label=&#34;Direct link to the section What is the actual bottleneck in developing with AI?&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Not the speed at which code appears. The bottleneck is &lt;strong&gt;trust&lt;/strong&gt;: code that compiles, whose tests are green and that reads correctly — and is wrong anyway. This class of defect accounts for almost every finding we have, and no standard pipeline sees it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Build test automation in house or contract it out?</title>
				<link>https://www-main.uat.aerea.de/en/insights/test-automation-in-house-or-external/</link>
				<pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-main.uat.aerea.de/en/insights/test-automation-in-house-or-external/</guid>
				<description>&lt;h2 id=&#34;wrong-question&#34;&gt;Why is the question framed wrongly?&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#wrong-question&#34;&#xA;     aria-label=&#34;Direct link to the section Why is the question framed wrongly?&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Test automation is not a project with an end but an estate with a maintenance load. The question is therefore not &amp;ldquo;who builds it&amp;rdquo; but &lt;strong&gt;&amp;ldquo;who maintains it in three years&amp;rdquo;&lt;/strong&gt;. Skip that and you buy a test suite that is red after two releases, then skipped, then switched off — and you pay for it twice.&lt;/p&gt;</description>
			</item>
			<item>
				<title>The guardrails we set for agents</title>
				<link>https://www-main.uat.aerea.de/en/insights/guardrails-for-agents/</link>
				<pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-main.uat.aerea.de/en/insights/guardrails-for-agents/</guid>
				<description>&lt;h2 id=&#34;core-question&#34;&gt;May an agent write code in a regulated project?&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#core-question&#34;&#xA;     aria-label=&#34;Direct link to the section May an agent write code in a regulated project?&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Yes — under the same conditions as a human. What matters is not who wrote the line but whether it is specified, reviewed, tested and released. Anyone who closes that chain can use agents. Anyone who opens it for agents has a problem with humans too.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Custom or standard software in energy management?</title>
				<link>https://www-main.uat.aerea.de/en/insights/custom-or-standard-software-energy-management/</link>
				<pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-main.uat.aerea.de/en/insights/custom-or-standard-software-energy-management/</guid>
				<description>&lt;h2 id=&#34;short-answer&#34;&gt;When is a standard product enough?&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#short-answer&#34;&#xA;     aria-label=&#34;Direct link to the section When is a standard product enough?&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;As long as your installation matches the picture the product was built for: one manufacturer, a manageable scope, an optimisation strategy from the catalogue. Then the manufacturer&amp;rsquo;s own system is practically unbeatable — available sooner, cheaper to enter, maintained by someone else. The tipping point almost never comes at purchase, but at the third special case.&lt;/p&gt;</description>
			</item>
			<item>
				<title>OPC UA or MQTT for machine connectivity?</title>
				<link>https://www-main.uat.aerea.de/en/insights/opc-ua-or-mqtt/</link>
				<pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-main.uat.aerea.de/en/insights/opc-ua-or-mqtt/</guid>
				<description>&lt;h2 id=&#34;core&#34;&gt;What is the difference in one sentence?&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#core&#34;&#xA;     aria-label=&#34;Direct link to the section What is the difference in one sentence?&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;OPC UA is an information model with a transport, MQTT is a transport without an information model.&lt;/strong&gt; OPC UA describes &lt;em&gt;what&lt;/em&gt; a value means — type, unit, membership, access rights. MQTT only moves it from A to B and leaves the meaning to your convention. Everything else follows from that single difference.&lt;/p&gt;</description>
			</item>
			<item>
				<title>E2E tests against real databases with Testcontainers</title>
				<link>https://www-main.uat.aerea.de/en/insights/e2e-tests-with-testcontainers/</link>
				<pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><author>info@aerea.de (AereA GmbH)</author>
				<guid>https://www-main.uat.aerea.de/en/insights/e2e-tests-with-testcontainers/</guid>
				<description>&lt;h2 id=&#34;why-real&#34;&gt;Why do we run end-to-end tests against a real database?&#xA;  &lt;a class=&#34;heading-anchor&#34; href=&#34;#why-real&#34;&#xA;     aria-label=&#34;Direct link to the section Why do we run end-to-end tests against a real database?&#34;&gt;&#xA;    &lt;span aria-hidden=&#34;true&#34;&gt;#&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Because a mock confirms the assumption you had while writing it, and a real database contradicts it. The failures that get expensive in distributed systems sit exactly where the mock knows nothing: in transaction boundaries, isolation levels, the ordering of migrations and the time zone behaviour of timestamps. A test against an in-memory substitute measures the substitute, not the system.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
