<?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 Zardoz Group | Cloud, AI &amp; Software Engineering Consultancy</title><link>https://zardozgroup.com/insights/</link><description>Recent content in Insights on Zardoz Group | Cloud, AI &amp; Software Engineering Consultancy</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://zardozgroup.com/insights/index.xml" rel="self" type="application/rss+xml"/><item><title>Swift 6.4: What Changes in the Code You Maintain</title><link>https://zardozgroup.com/insights/swift-6-4-practical-upgrade/</link><pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate><guid>https://zardozgroup.com/insights/swift-6-4-practical-upgrade/</guid><description>&lt;p&gt;When I look at a language release, I want to know what it does for the code someone has to maintain after the release announcement stops being interesting.&lt;/p&gt;&#10;&lt;p&gt;Does it make resource ownership clearer? Does it remove another opportunity to forget cleanup? Can a team adopt it without rewriting every test helper at once?&lt;/p&gt;&#10;&lt;p&gt;Swift 6.4 has useful answers to those questions. It was released on September 15, 2026, and the improvements extend well beyond Apple application development. Here I want to concentrate on changes you can see in ordinary application and library code. &lt;a href="https://www.swift.org/blog/swift-6.4-released/"&gt;Swift 6.4 release announcement&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Creating Resumes with Impact</title><link>https://zardozgroup.com/insights/creating-resumes-with-impact/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://zardozgroup.com/insights/creating-resumes-with-impact/</guid><description>&lt;p&gt;I get asked for advice on resumes all the time. People want to know whether the format is right, whether they should shorten it, or whether they have included the right technologies.&lt;/p&gt;&#10;&lt;p&gt;Those are reasonable questions. But before worrying about the font, I want to know what the resume tells me about the work.&lt;/p&gt;&#10;&lt;p&gt;You maintained a platform. You wrote scripts. You participated in architecture reviews. You managed a team.&lt;/p&gt;</description></item><item><title>What You Leave Behind</title><link>https://zardozgroup.com/insights/what-you-leave-behind/</link><pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate><guid>https://zardozgroup.com/insights/what-you-leave-behind/</guid><description>&lt;p&gt;Years ago, people used to say something about certain employees:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;You cannot get fired, but you also cannot get promoted.&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;The idea was that the person knew too much. They were the only one who understood the system, the customer, the process, or the collection of scripts holding everything together. The company could not afford to lose them. Unfortunately, it could not afford to move them either.&lt;/p&gt;&#10;&lt;p&gt;It sounds almost flattering. It is not.&lt;/p&gt;</description></item><item><title>When PARRY Met DOCTOR Again: Recreating RFC 439 with Local LLMs</title><link>https://zardozgroup.com/insights/when-parry-met-doctor-again/</link><pubDate>Fri, 28 Aug 2026 00:00:00 +0000</pubDate><guid>https://zardozgroup.com/insights/when-parry-met-doctor-again/</guid><description>&lt;p&gt;In January 1973, Vint Cerf published what may be the most charming document in the history of the internet. &lt;a href="https://www.rfc-editor.org/rfc/rfc439"&gt;RFC 439, titled &amp;ldquo;PARRY Encounters the DOCTOR,&amp;rdquo;&lt;/a&gt; is a transcript of a conversation that took place on September 18, 1972, between two computer programs connected over ARPANET - one running at Stanford, one at BBN in Cambridge. It opens like this:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;Good Evening. Tell me your problems.&lt;/p&gt;&#10;&lt;p&gt;*People get on my nerves sometimes.&lt;/p&gt;&#10;&lt;p&gt;I am not sure I understand you fully.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>