<?xml version="1.0" encoding="UTF-8" ?> <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel> <title>Paul Withers&#39; Blog</title><description>A blog about various HCL software, software development and related learning, from an Lifetime IBM Champion and former HCL Lifetime Ambassador</description><link>https://paulswithers.github.io/</link><atom:link href="https://paulswithers.github.io/feed_rss_created.xml" rel="self" type="application/rss+xml" /> <managingEditor>Paul S. Withers</managingEditor><docs>https://github.com/paulswithers/paulswithers.github.io</docs><language>en</language> <pubDate>Tue, 24 Feb 2026 17:40:54 -0000</pubDate> <lastBuildDate>Tue, 24 Feb 2026 17:40:54 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.17.9</generator> <image> <url>None</url> <title>Paul Withers' Blog</title> <link>https://paulswithers.github.io/</link> </image> <item> <title>Is “AGENTS.md Engineering” The Next Optimisation Approach?</title> <description>&lt;h1&gt;Is “AGENTS.md Engineering” The Next Optimisation Approach?&lt;/h1&gt; &lt;p&gt;AGENTS.md has become the de facto standard for directing your agent. Claude Code had CLAUDE.md but with AGENTS.md becoming part of the &lt;a href=&#34;https://aaif.io/&#34;&gt;Agentic AI Foundation&lt;/a&gt; last year, even Claude Code now recognises and uses AGENTS.md. But the benefits of AGENTS.md are now being discussed and challenged in academic circles. However, maybe what’s being discussed is just the &lt;em&gt;first&lt;/em&gt; iteration. And just as the AI world went through Prompt Engineering and then Context Engineering, maybe the next phase (or &lt;em&gt;a&lt;/em&gt; next phase) is “AGENTS.md Engineering”.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2026/02/23/agentsmd-engineering/</link> <pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2026/02/23/agentsmd-engineering/</guid> </item> <item> <title>Lessons in Effecting Change - How We Got A Domino Non-Production Server License</title> <description>&lt;h1&gt;Lessons in Effecting Change - How We Got A Domino Non-Production Server License&lt;/h1&gt; &lt;p&gt;More than ten years ago, Christian Guedemann and I worked with various IBMers to try to get a free Domino server entitlement for developers. It took time - not an unacceptable amount of time, in my personal opinion - but we got more than we hoped. The dev and test server license is no longer available, because licensing for customers changed. Some are critical of that decision. But none, as far as I’m aware, have demonstrated taken the &lt;a href=&#34;./2026-02-19-ai-high-agency.md&#34;&gt;high-agency mindset&lt;/a&gt; that Christian and I demonstrated and which is crucial to effect change.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2026/02/22/effecting-change/</link> <pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2026/02/22/effecting-change/</guid> </item> <item> <title>Transforming Software with AI</title> <description>&lt;h1&gt;Transforming Software with AI&lt;/h1&gt; &lt;p&gt;The ability of AI to generate software applications has taken gigantic leaps forward in just the last few months. A team of agents using Claude Opus 4.6 wrote a C compiler with minimal human interaction. In the &lt;a href=&#34;https://www.anthropic.com/news/claude-opus-4-6&#34;&gt;press release for Opus 4.6&lt;/a&gt; Anthropic build Claude with Claude. I personally use coding agents more and more, and I’ve seen significant rapid application development with AI.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2026/02/21/ai-transforming-software/</link> <pubDate>Sat, 21 Feb 2026 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2026/02/21/ai-transforming-software/</guid> </item> <item> <title>AI and The High-Agency Mindset</title> <description>&lt;h1&gt;AI and The High-Agency Mindset&lt;/h1&gt; &lt;p&gt;It was only late last year that I heard the term &#34;high-agency mindset&#34;, even though it&#39;s nearly a decade old. But after learning about it, I started to recognise signs to some extent in myself and some others I know. It became understandable why high-agency individuals surround themselves with other high-agency individuals, and why they can become frustrated with low-agency individuals. Where others see blockers and wait for (or expect) someone else to clear them, high-agency mindset individuals can see solutions or expect people to take responsibility for resolving them - or else they just go around them. It’s a mindset that aligns well with the concept of &lt;a href=&#34;https://www.bitesizelearning.co.uk/resources/directly-responsible-individual-dri-apple&#34;&gt;Directly Responsible Individuals or DRIs&lt;/a&gt;.&lt;/p&gt; &lt;p&gt;But it also became apparent that AI could have a big impact on the future of the two high-agency and lower-agency individuals.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2026/02/19/ai-high-agency/</link> <pubDate>Thu, 19 Feb 2026 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2026/02/19/ai-high-agency/</guid> </item> <item> <title>AI and Marketing Content</title> <description>&lt;h1&gt;AI and Marketing Content&lt;/h1&gt; &lt;h2&gt;The Microsoft Revolution&lt;/h2&gt; &lt;p&gt;About 20 years ago there was a major shift in document processing which had profound repercussions for the AI world, years before it started. With Office 2007, Microsoft made a major change in their document formats. Up until that point, Microsoft had preferred closed, proprietary, customer lock-in of content into silos of information. But during the 2000s the rise of Apache OpenOffice and its open document formats, along with governmental demands for interoperability, put pressure on Microsoft to introduce OOXML. Of course it had added benefits - competition alone rarely encourages change. The new format was up to 75% smaller, improved corruption recovery and improved security.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2026/02/01/ai-and-marketing/</link> <pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2026/02/01/ai-and-marketing/</guid> </item> <item> <title>AI, Tailwind, and The Future of Media</title> <description>&lt;h1&gt;AI, Tailwind, and The Future of Media&lt;/h1&gt; &lt;p&gt;Recently there was an announcement that Tailwind was laying off 75% (3 of 4) of its engineering team because of revenue collapse. The initial hint came from a &lt;a href=&#34;https://github.com/tailwindlabs/tailwindcss.com/pull/2388#issuecomment-3715074726&#34;&gt;comment on a PR&lt;/a&gt; and was followed up with a podcast on X. This has caused a lot of discussion in the IT world. But I want to take a different approach. What does this mean for the media industry and the future of how we find out news?&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2026/01/12/ai-and-media/</link> <pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2026/01/12/ai-and-media/</guid> </item> <item> <title>AI Coding - Thoughts About The Future of Development</title> <description>&lt;h1&gt;AI Coding - Thoughts About The Future of Development&lt;/h1&gt; &lt;p&gt;&lt;a href=&#34;https://en.wikipedia.org/wiki/Vibe_coding&#34;&gt;&lt;strong&gt;Vibe coding&lt;/strong&gt;&lt;/a&gt; is probably the term of the year. Since being coined by Andrej Karpathy in a tweet in February the term has gained widespread adoption. My job is research, so I&#39;m not one to accept code without review. But I absolutely need to be aware of new technologies and approaches, and evaluate their usefulness. And all technologies improve over time. So AI-assisted coding has been a regular part of my work for 18 months. Over recent weeks I&#39;ve used it more and more, for a wide variety of purposes. And research is not just about trying things, it&#39;s about extrapolating and anticipating future usage.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/12/14/ai-coding-futures/</link> <pubDate>Sun, 14 Dec 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/12/14/ai-coding-futures/</guid> </item> <item> <title>Effective AI Usage: Managing Hallucination</title> <description>&lt;h1&gt;Effective AI Usage: Managing Hallucination&lt;/h1&gt; &lt;p&gt;One of the biggest challenges when working with AI is hallucination. I&#39;ve encountered and fought against it. It&#39;s worth discussing what can and can&#39;t be done to solve the problem.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/10/26/effective-ai-4/</link> <pubDate>Sun, 26 Oct 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/10/26/effective-ai-4/</guid> </item> <item> <title>Effective AI Usage: Understanding Brains</title> <description>&lt;h1&gt;Effective AI Usage: Understanding Brains&lt;/h1&gt; &lt;p&gt;I&#39;ve talked about the (current) &lt;a href=&#34;./2025-08-16-ai-lessons.md&#34;&gt;moving parts of AI&lt;/a&gt; and &lt;a href=&#34;./2025-09-15-barriers-to-effective-ai-2.md&#34;&gt;AI-fu&lt;/a&gt;. But a fundamental aspect of AI-fu is being aware of how we think and how that&#39;s different to how LLMs &#34;think&#34;. It&#39;s probably true that most people are not consciously aware of how they think or aware of how colleagues thinking works differently. So it&#39;s well worth raising that topic, because it&#39;s crucial to the quality of results.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/10/05/effective-ai-3/</link> <pubDate>Sun, 05 Oct 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/10/05/effective-ai-3/</guid> </item> <item> <title>Effective AI Usage: AI-fu</title> <description>&lt;h1&gt;Effective AI Usage: AI-fu&lt;/h1&gt; &lt;p&gt;In &lt;a href=&#34;./2025-09-08-effective-ai-1.md&#34;&gt;my last blog post&lt;/a&gt; I talked about the many aspects of modern AI and the importance of understanding them all. But even more important than this is what I am terming &#34;AI-fu&#34;. So what is AI-fu?&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/09/15/effective-ai-2/</link> <pubDate>Mon, 15 Sep 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/09/15/effective-ai-2/</guid> </item> <item> <title>XPages App to Web App: Part 20: Custom CSP Settings</title> <description>&lt;h1&gt;XPages App to Web App: Part 20: Custom CSP Settings&lt;/h1&gt; &lt;p&gt;A good web server will enforce &lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP&#34;&gt;Content Security Policy&lt;/a&gt; settings. If you are using something like Express as the web server, the endpoints will set that Content Security Policy. In the case of Single Page Applications hosted on Domino REST API, since release 1.15 by default a strict CSP is applied. But it is possible to change the CSP settings per application.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/09/14/framework-web-20/</link> <pubDate>Sun, 14 Sep 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/09/14/framework-web-20/</guid> </item> <item> <title>Effective AI Usage Part One - What is AI?</title> <description>&lt;h1&gt;Effective AI Usage Part One - What is AI?&lt;/h1&gt; &lt;p&gt;In &lt;a href=&#34;./2025-08-16-ai-lessons.md&#34;&gt;my last blog post&lt;/a&gt; I talked about some lessons I&#39;ve learned from using AI. I talked about a follow-up article talking about AI use at a higher level. Recent experience has reinforced my thinking on this. In this blog post we&#39;re going to focus on what AI is, the initial interaction, and training.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/09/08/effective-ai-1/</link> <pubDate>Mon, 08 Sep 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/09/08/effective-ai-1/</guid> </item> <item> <title>More AI Lessons</title> <description>&lt;h1&gt;More AI Lessons&lt;/h1&gt; &lt;p&gt;A little while ago I blogged on &lt;a href=&#34;./2025-06-30-rapid-development.md&#34;&gt;developing at speed&lt;/a&gt;. The obvious omission from all aspects was &lt;strong&gt;AI&lt;/strong&gt;. But AI – like an IDE – is just a tool. Unless you understand what it can and can&#39;t provide, unless you use it intelligently, you will not reap the benefits. But unlike an IDE, AI doesn&#39;t come with a set of menus that hint at what it can and can&#39;t do. AI doesn&#39;t come with a marketplace of extensions that provide functionality shared by the community. And it&#39;s so new that we&#39;re all working it out. So what are my thoughts?&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/08/16/ai-lessons/</link> <pubDate>Sat, 16 Aug 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/08/16/ai-lessons/</guid> </item> <item> <title>Supercharging Input to Domino REST API Agents</title> <description>&lt;h1&gt;Supercharging Input to Domino REST API Agents&lt;/h1&gt; &lt;p&gt;One of the things I learned when building &lt;a href=&#34;https://github.com/HCL-TECH-SOFTWARE/volt-mx-ls-toolkit&#34;&gt;HCL Volt MX LotusScript Toolkit&lt;/a&gt; was that calling a web agent with &lt;code&gt;?OpenAgent&lt;/code&gt; URL populates the &lt;code&gt;NotesSession.DocumentContext&lt;/code&gt; with various fields containing useful information from the request. So when I was building agent processing functionality into the POC that became Domino REST API, I utilised the same approach to provide opportunities to pass contextual information across to an agent.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/08/05/drapi-agents/</link> <pubDate>Tue, 05 Aug 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/08/05/drapi-agents/</guid> </item> <item> <title>Developing at Speed</title> <description>&lt;h1&gt;Developing at Speed&lt;/h1&gt; &lt;p&gt;One of the main outputs of research development is the proof of concept. An early lesson I picked up when I joined HCL Labs was to deliver working code, not slides. And the key when building a proof of concept is speed. In some cases, it may end up proving why an approach &lt;em&gt;won&#39;t&lt;/em&gt; work. In many scenarios, it may end up being put on a shelf indefinitely. Even if the concept proves appealing, the implementation choices may not be the preferred option for the final solution. So speed is of the essence: spending a couple of weeks building something that goes nowhere is acceptable; spending a couple of months is not. So the ability to get maximum results in the minimum time is key.&lt;/p&gt; &lt;p&gt;But how do you do that?&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/06/30/rapid-development/</link> <pubDate>Mon, 30 Jun 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/06/30/rapid-development/</guid> </item> <item> <title>Adventures in Rust</title> <description>&lt;h1&gt;Adventures in Rust&lt;/h1&gt; &lt;p&gt;One of my core principles for IT research development can be summed up by a saying more than 2500 years old, attributed to &lt;a href=&#34;https://en.wikipedia.org/wiki/Solon&#34;&gt;Solon&lt;/a&gt; and appearing twice in Plutarch’s Life of Solon: “I grow old always learning many things”. In many ways, to stop learning is to stop living.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/06/15/rust/</link> <pubDate>Sun, 15 Jun 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/06/15/rust/</guid> </item> <item> <title>2025 05 18 engage 2025</title> <description>&lt;p&gt;This week, once again, I will be speaking at Engage in Den Haag. As usual, it promises to be a great conference. And as usual, I will be busy.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/05/18/engage-2025/</link> <pubDate>Sun, 18 May 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/05/18/engage-2025/</guid> </item> <item> <title>Shu-Ha-Ri</title> <description>&lt;h1&gt;Shu-Ha-Ri&lt;/h1&gt; &lt;p&gt;Some months ago &lt;a href=&#34;https://wissel.net&#34;&gt;Stephan Wissel&lt;/a&gt; pointed me to &lt;a href=&#34;https://martinfowler.com/bliki/ShuHaRi.html&#34;&gt;an article on Shu-Ha-Ri&lt;/a&gt;, which refers to Alistair Cockburn&#39;s &lt;a href=&#34;https://www.amazon.com/Agile-Software-Development-Cooperative-Game-ebook/dp/B0027976NG&#34;&gt;Agile Software Development&lt;/a&gt;. It&#39;s well worth software developers being aware of the concept, because it is crucial to the developer&#39;s life journey.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/05/15/shu-ha-ri/</link> <pubDate>Thu, 15 May 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/05/15/shu-ha-ri/</guid> </item> <item> <title>Domino REST API, CORS and Regex</title> <description>&lt;h1&gt;Domino REST API, CORS and Regex&lt;/h1&gt; &lt;p&gt;Release 1.1.3.1 of Domino REST API introduces &lt;a href=&#34;https://opensource.hcltechsw.com/Domino-rest-api/whatsnew/v1.1.3.html#cors-is-now-using-regex&#34;&gt;a breaking change in CORS handling&lt;/a&gt;. This makes configuration less straightforward, but as the documentation states, it increases the flexibility and probably makes things a lot easier for larger environments. And though regex is not something Domino developers work with regularly, there are tools close to home that can help.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/05/01/drapi-cors-regex/</link> <pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/05/01/drapi-cors-regex/</guid> </item> <item> <title>Using AI</title> <description>&lt;h1&gt;Using AI&lt;/h1&gt; &lt;p&gt;As a researcher, I&#39;m always looking to learn, to expand the toolbag I have, and find innovative ways to improve outcomes. Even when AI is not at the heart of the project I&#39;m working on, I&#39;m constantly looking for ways it can make my life easier and life easier for developers using what I create. And the fact that we targeted a standard IDE means the effort required to integrate AI is reduced. But as with any new tool, it&#39;s important to learn what it can do and what it can&#39;t. And work this week has shown me that this requires a diligent approach.&lt;/p&gt;</description> <link>https://paulswithers.github.io/blog/2025/04/26/using-ai/</link> <pubDate>Sat, 26 Apr 2025 00:00:00 +0000</pubDate> <source url="https://paulswithers.github.io/feed_rss_created.xml">Paul Withers' Blog</source><guid isPermaLink="true">https://paulswithers.github.io/blog/2025/04/26/using-ai/</guid> </item> </channel> </rss>