<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Swiftui on Ronan O Ciosoig</title><link>https://ronanoc.dev/tags/swiftui/</link><description>Recent content in Swiftui on Ronan O Ciosoig</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 04 Oct 2026 23:30:43 +0000</lastBuildDate><atom:link href="https://ronanoc.dev/tags/swiftui/index.xml" rel="self" type="application/rss+xml"/><item><title>Don't Make It Public. Give It a Boundary</title><link>https://ronanoc.dev/articles/2026/dont-make-it-public/</link><pubDate>Sun, 04 Oct 2026 23:30:43 +0000</pubDate><guid>https://ronanoc.dev/articles/2026/dont-make-it-public/</guid><description>&lt;figure&gt;&lt;img src="https://ronanoc.dev/articles/2026/dont-make-it-public/image-1.jpeg"&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;p&gt;A module can already be right about what’s internal and still be wrong about what’s public. In this article I explore what should go in the API for a pure SwiftUI module, the syntax to make it work, and the reasoning behind it.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;This is the third part of a series about how to enhance validation in the agentic loop. &lt;em&gt;See the accompanying code repo on &lt;em&gt;&lt;a href="https://github.com/ronanociosoig/Shopapp"&gt;&lt;em&gt;Github here&lt;/em&gt;&lt;/a&gt;&lt;/em&gt;.&lt;/em&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;h2 id="faster-ux-review"&gt;Faster UX review&lt;/h2&gt;&#10;&lt;p&gt;I was working on the checkout flow. It was a funnel of the following screens: shopping cart, address, delivery and extras, payment method, card entry, processing, and confirmation. What I needed to iterate on back then was a new payment method. It was tedious to have to click through all the screens each time, so I decided to add a scenario in the micro-app for payment methods, giving direct access to each step.&lt;/p&gt;</description></item><item><title>AI Writes Fast. Your Safety Net Needs to Be Faster.</title><link>https://ronanoc.dev/articles/2026/ai-writes-fast/</link><pubDate>Sat, 01 Aug 2026 12:37:28 +0000</pubDate><guid>https://ronanoc.dev/articles/2026/ai-writes-fast/</guid><description>&lt;figure&gt;&lt;img src="https://ronanoc.dev/articles/2026/ai-writes-fast/image-1.jpeg"&gt;&#10;&lt;/figure&gt;&#10;&#10;&lt;p&gt;I’ve been writing code for the past year switching between Copilot, Claude Code and Codex (sorry Cursor, it just didn’t happen). With these tools, building a flow of screens for an app — the UI, the model, a first pass at test coverage — takes minutes instead of days.&lt;/p&gt;&#10;&lt;p&gt;What hasn’t gotten any faster is what happens next: the review process of the code changes before merging it into a large, live production project. It has to be manually reviewed line by line. Am I confident that an agent-generated PR is correct? Definitely not. It generates plausible code that compiles, but often has a subtle change that isn’t correct. In general, the higher velocity output in generated code has led to more bugs — AI-generated code creates 1.7x more problems than human-written code, per CodeRabbit’s analysis.&lt;/p&gt;</description></item></channel></rss>