<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Claude on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/claude/</link><description>Recent content in Claude on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 13 Feb 2026 07:00:02 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/claude/index.xml" rel="self" type="application/rss+xml"/><item><title>Can GenAI Help Reduce Energy Used by Java Code?</title><link>https://javapro-en.svenruppert.com/can-genai-help-reduce-energy-used-by-java-code/</link><pubDate>Fri, 13 Feb 2026 07:00:02 +0000</pubDate><guid>https://javapro-en.svenruppert.com/can-genai-help-reduce-energy-used-by-java-code/</guid><description>&lt;p&gt;Some recent studies show that IT is emitting &lt;a href="https://www.globenewswire.com/news-release/2022/05/31/2453416/0/en/The-Carbon-Footprint-of-Brands-Online-Advertising-Campaigns-is-Significant-fifty-five-Study-Reveals.html"&gt;more CO2 than civil aviation&lt;/a&gt;! As software developers, there is something we can do: optimising our code. &lt;strong&gt;Making our code run more efficiently should reduce the carbon footprint of IT.&lt;/strong&gt; It will consume less CPU, RAM, disk, and network. Hardware being powered by electricity, these optimisations should reduce our electricity bills and lower emissions due to generation of that electricity. Optimised software also extends hardware lifespan by reducing the need for upgrades, diminishing the embodied carbon from manufacturing and avoiding raw material extraction (e.g., rare earths mining).&lt;/p&gt;</description></item><item><title>Are AI coding tools worth it? - part 1</title><link>https://javapro-en.svenruppert.com/are-ai-coding-tools-worth-it-part-1/</link><pubDate>Thu, 17 Oct 2024 10:00:00 +0000</pubDate><guid>https://javapro-en.svenruppert.com/are-ai-coding-tools-worth-it-part-1/</guid><description>&lt;p&gt;This is the start of a few posts about AI coding tools. This one sets the scene and gives a taste of what I found. In later posts I&amp;rsquo;ll show more of what I got from using them &lt;em&gt;as is.&lt;/em&gt; , explore what the sweet spots might be and end with a harder look at getting value out of them. If you want to skip to the end go &lt;a href="https://javapro.io/2024/11/07/1-billion-record-challenge-ai-style/"&gt;here&lt;/a&gt;&lt;/p&gt;
&lt;h4 id="a-long-time-ago-in-a-company-far-far-away"&gt;&lt;strong&gt;A long time ago, in a company far, far away…&lt;/strong&gt;&lt;/h4&gt;
&lt;p&gt; In the very early 90&amp;rsquo;s I had the, well, honour is not quite the word I want, the experience may be, to use a prototype of one of the first viable commercial speech-to-text and speech-to-control tools.  I used it at work; I used it at home. It was a disaster in all ways.  In the first go-around, the training for learning your voice was arduous, literally painful, and demanding. In the second prototype, it would often pick up the sound of the hard disk on the computer and interpret it as text, to much hilarity for all. &lt;/p&gt;</description></item></channel></rss>