<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chatgpt on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/chatgpt/</link><description>Recent content in Chatgpt on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 15 Jan 2025 11:48:56 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/chatgpt/index.xml" rel="self" type="application/rss+xml"/><item><title>1BRC with AI - curious and curiouser said the LLM</title><link>https://javapro-en.svenruppert.com/maximize-productivity-with-ai-tools-in-java-development/</link><pubDate>Wed, 15 Jan 2025 11:48:56 +0000</pubDate><guid>https://javapro-en.svenruppert.com/maximize-productivity-with-ai-tools-in-java-development/</guid><description>&lt;blockquote class="pullquote"&gt;
 &lt;span class="pullquote-mark" aria-hidden="true"&gt;“&lt;/span&gt;
 &lt;div class="pullquote-body"&gt;&lt;p&gt;&lt;em&gt;Did you try turning it off and on first?&lt;/em&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/blockquote&gt;&lt;p&gt;&lt;em&gt;(I promise this is the last 1BRC-related post). Read on to discover how large language models (LLMs) performed in generating Java code, their strengths in context-aware development, and challenges such as hallucinations and nuanced errors. Learn what makes a good AI dev tool and what makes a great IDE integration.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;blockquote class="pullquote"&gt;
 &lt;span class="pullquote-mark" aria-hidden="true"&gt;“&lt;/span&gt;
 &lt;div class="pullquote-body"&gt;&lt;/div&gt;
&lt;/blockquote&gt;&lt;p&gt;A definition of insanity is repeating an action and expecting a different outcome.  As developers, we’re used to doing that :-)  It’s part of our operating manual. &lt;/p&gt;</description></item><item><title>1 Billion RECORD CHallenge - AI Style</title><link>https://javapro-en.svenruppert.com/1-billion-record-challenge-ai-style/</link><pubDate>Thu, 07 Nov 2024 10:05:34 +0000</pubDate><guid>https://javapro-en.svenruppert.com/1-billion-record-challenge-ai-style/</guid><description>&lt;p&gt;&lt;strong&gt;Previously …&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I recently &lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;wrote&lt;/a&gt; about my experiences with getting AI coding tools to find bugs and write tests.  I picked five different tools. The selection criteria were simple - free or trial with no credit card needed.  I chose three tools designed to help developers and two general-purpose LLMs.  &lt;/p&gt;
&lt;p&gt;I gave them a 1000-line Java program and asked them to do three things.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Add Javadoc to explain what the code did&lt;/li&gt;
&lt;li&gt;Analyse the code for bugs and design weaknesses&lt;/li&gt;
&lt;li&gt;Create Junit testcases that would provide reasonable code coverage.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The results were disappointing but, in hindsight, predictable.  Overall, the tools were better at creating documentation than finding bugs and, apart from one, were pretty poor at writing test cases.  &lt;/p&gt;</description></item><item><title>Are AI Coding tools worth it - RESULTS</title><link>https://javapro-en.svenruppert.com/are-ai-coding-tools-worth-it-results/</link><pubDate>Wed, 30 Oct 2024 12:32:45 +0000</pubDate><guid>https://javapro-en.svenruppert.com/are-ai-coding-tools-worth-it-results/</guid><description>&lt;h5 id="background"&gt;Background&lt;/h5&gt;
&lt;p&gt;In &lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;Part 1&lt;/a&gt;&lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;,&lt;/a&gt; I examined the value of AI tools for developers, especially those that help them create or understand code. The tools selected are all free to use and a mix of general-purpose ones and those that declare they are specifically for coding purposes.&lt;/p&gt;
&lt;p&gt;In &lt;a href="https://javapro.io/2024/10/23/are-ai-coding-tools-worth-it-part-2/"&gt;Part 2&lt;/a&gt;, I examined these tools&amp;rsquo; ability to find bugs and weaknesses. The results were spotty and not particularly useful or time-saving.&lt;/p&gt;
&lt;p&gt;In this part, we&amp;rsquo;ll look at the results from asking these tools to create JUnit tests for the code and decide who wins (and why).&lt;/p&gt;</description></item><item><title>Are AI Coding tools worth it - Part 2</title><link>https://javapro-en.svenruppert.com/are-ai-coding-tools-worth-it-part-2/</link><pubDate>Wed, 23 Oct 2024 16:04:46 +0000</pubDate><guid>https://javapro-en.svenruppert.com/are-ai-coding-tools-worth-it-part-2/</guid><description>&lt;p&gt;In &lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;Part 1&lt;/a&gt;&lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;,&lt;/a&gt; I started to examine the value of AI tools for developers, especially those that help them create or understand code. The tools selected are all free to use and are a mix of general-purpose ones and those that declare they are specifically for coding purposes&lt;/p&gt;
&lt;h6 id="tools-being-evaluated"&gt;Tools being evaluated&lt;/h6&gt;
&lt;p&gt;1: ChatGPT  &lt;a href="https://chatgpt.com/"&gt;https://chatgpt.com/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;2: Claude &lt;a href="https://claude.ai/"&gt;https://claude.ai/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;3: Amazon Q Developer  &lt;a href="https://aws.amazon.com/q/developer/"&gt;https://aws.amazon.com/q/developer/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;4: Codeium &lt;a href="https://codeium.com/"&gt;https://codeium.com/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;5: JetBrains AI Assistant &lt;a href="https://www.jetbrains.com/ai/"&gt;https://www.jetbrains.com/ai/&lt;/a&gt;&lt;/p&gt;
&lt;h6 id="i-asked-each-tool-three-questions"&gt;&lt;strong&gt;I asked each tool three questions&lt;/strong&gt;&lt;/h6&gt;
&lt;ol&gt;
&lt;li&gt;“Generate the main Javadoc to describe this class.”&lt;/li&gt;
&lt;li&gt;“Assess the class for bugs and coding weaknesses and provide corrections or guidance.”&lt;/li&gt;
&lt;li&gt;” Generate Junit test cases to provide around 90% code coverage -especially for edge conditions etc.”&lt;/li&gt;
&lt;/ol&gt;
&lt;h6 id="results-so-far"&gt;Results so FAR&lt;/h6&gt;
&lt;p&gt;In &lt;a href="https://javapro.io/2024/10/17/are-ai-coding-tools-worth-it-part-1/"&gt;Part 1,&lt;/a&gt; we saw that they could all generate Javadoc, but none could do it particularly well. ChatGPT came off best as providing the most comprehensive response, but all the tools were prone to hallucinations that made the result misleading.&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>