<rss version="2.0">
  <channel>
    <title>Dialogue on Leon Mika</title>
    <link>https://lmika.org/categories/dialogue/</link>
    <description></description>
    
    <language>en</language>
    
    <lastBuildDate>Fri, 20 Feb 2026 12:57:22 +1100</lastBuildDate>
    
    <item>
      <title>Dialogue: LLM Auto-complete Is…</title>
      <link>https://lmika.org/2026/02/20/dialogue-llm-autocomplete-is.html</link>
      <pubDate>Fri, 20 Feb 2026 12:57:22 +1100</pubDate>
      
      <guid>http://lmika.micro.blog/2026/02/20/dialogue-llm-autocomplete-is.html</guid>
      <description>&lt;style&gt;
.dialogue.dialogue-2026-02-the-frustrations-of {
    --dialogue-m1-color: #4C6C8C;
    --dialogue-m1-background: no-repeat center / 105% url(https://avatars.micro.blog/avatars/2024/15/55331.jpg);
    --dialogue-m2-color: #625309;
    --dialogue-m2-background: white no-repeat center / 75% url(https://lmika.org/uploads/2025/rubber-duck.jpg);
}
&lt;/style&gt;
&lt;div class=&#34;dialogue dialogue-2026-02-the-frustrations-of&#34;&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; You writing code?&lt;/p&gt;
&lt;p class=&#34;member member-m1&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Author:&lt;/b&gt; Documentation.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; And you&#39;re using an…&lt;/p&gt;
&lt;p class=&#34;member member-m1&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Author:&lt;/b&gt; IDE? Yes, I am.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Do you have that…&lt;/p&gt;
&lt;p class=&#34;member member-m1&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Author:&lt;/b&gt; LLM-powered auto complete? I do, yes. And it&#39;s fine, although it does seem like the IDE&#39;s…&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Always trying to finish your sentences?&lt;/p&gt;
&lt;p class=&#34;member member-m1&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Author:&lt;/b&gt; Yes. It can be quite…&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Bothersome? Yeah, I can&#39;t imagine how that must feel. 😛&lt;/p&gt;
&lt;/div&gt;
</description>
    </item>
    
    <item>
      <title>Dialogue: Good Banter Not Found</title>
      <link>https://lmika.org/2025/12/19/dialogue-good-banter-not-found.html</link>
      <pubDate>Fri, 19 Dec 2025 14:52:51 +1100</pubDate>
      
      <guid>http://lmika.micro.blog/2025/12/19/dialogue-good-banter-not-found.html</guid>
      <description>&lt;style&gt;
.dialogue.dialogue-2025-12-404-errors {
    --dialogue-m1-color: #4C6C8C;
    --dialogue-m1-background: no-repeat center / 105% url(https://avatars.micro.blog/avatars/2024/15/55331.jpg);
    --dialogue-m2-color: #625309;
    --dialogue-m2-background: white no-repeat center / 75% url(https://lmika.org/uploads/2025/rubber-duck.jpg);
    --dialogue-m3-color: #325f04;
    --dialogue-m3-background: white no-repeat center / 75% url(https://lmika.org/uploads/2025/dialogue-avatar-turtle.jpg);
}
&lt;/style&gt;
&lt;div class=&#34;dialogue dialogue-2025-12-404-errors&#34;&gt;
&lt;p class=&#34;member direction&#34;&gt;&lt;i&gt;Duck is typing on a laptop when Tortoise arrives.&lt;/i&gt;&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Good day, Duck.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Good day, Tortoise. What a splendid day it is. I see that you are alone?&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Indeed. I tried reaching the author but he couldn&#39;t be found.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Ah, a regrettable scenario. But not one that is worthy of panic.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Curious that you were to say that, as I have been thinking of REST API design recently.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Oh, you too. For you see, I am working on such an API myself. Would you like to see it?&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Not right now, although I did show the author mine, as I wanted his opinion on something.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Oh, do tell.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Well, this API deals with users, you see. And some users pay for the service, and some don&#39;t. And I&#39;ve been tasked with coding an endpoint that&#39;ll answer which is which.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;To do this, the service is to receive a user ID, and if the user is paying, it is to return the billing information along with a 200 OK.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Okay, that&#39;s pretty straightforward.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; But what if the user is not a customer? What should the API return then?&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Well, I&#39;d imagine a 404 Not Found would do.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; That&#39;s what the author suggested, but when I proposed this to the team, they were unhappy.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Unhappy, how?&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; They told me 404 Not Found should be reserved for errors. They said that they&#39;ve got monitoring in place to catch these errors, and if I were to use it to signal a non-paying user, it&#39;ll throw off all these alarms.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Ah, yes. The &#34;only 200 OK is okay&#34; approach to monitoring. Understandable.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Oh, so you agree with their concerns?&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Well, I said I understand them. For there are a number of 4xx error codes that are worthy of knowing about sooner rather than later. A significant jump in 401 Unauthorized may be of interest to these operators.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; I guess. But isn&#39;t that what the 404 is for? Just because it can&#39;t be found doesn&#39;t mean that it&#39;s an error.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Yes, but at the same time, just because it may not be an error, doesn&#39;t necessarily mean it never is. Should a deployment go bad, and a URL is miss-configured, wouldn&#39;t you want to know straight away?&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; That&#39;s the argument they made, and I don&#39;t have a good counter. Using 404 Not Found feels right to me. It&#39;s REST-y. But I also understand their concerns about the monitoring. Oh, Mr D. I&#39;m at a loss of what to do.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Well, some practical thinking may be worth considering. I assume you are using JSON, right?&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Yes, that&#39;s correct.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; So could you, for example, return an empty JSON object if the billing information is not found? Or maybe a boolean saying whether billing information exists or not, along with the information is available? Maybe a pattern along the same lines if multiple users are required, and if none of them are paying, you can simply return an empty array. Each could be done with a 200 OK response.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;Of course, it may not be true to the idea of REST. But such is the limitations of using error codes for both business logic, such as saying a user is not paying; and control logic, such as when the endpoint is misconfigured.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; I see. Well this has been enlightening. Thank you, Mr. D. By the way, was this the same problem you were seeing?&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Oh, no. For you see, I took the bold step of shaking off REST in favour of gRPC.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Really? gRPC?&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Yes. It eliminates the problem entirely, as it separates the absence of something (NOT_FOUND) from the absence of the service itself (UNIMPLEMENTED, INTERNAL).&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Oh, how cleaver of you! I wonder if I can convince my team to switch. What an enviable position to be in.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Well, the envy may be all mine. For I am having a devil of a time trying to get the code generator to work. And when you are tasked with debugging an endpoint that is producing an incorrect response, and all you see is unreadable binary data; well, you may be singing a different tune.&lt;/p&gt;
&lt;p class=&#34;member member-m3&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Tortoise:&lt;/b&gt; Well, I will sure be singing a different tune as I head off home and ponder the suggestions you gave me. I will leave you to your errant tool chain. Good day, Duck.&lt;/p&gt;
&lt;p class=&#34;member member-m2&#34;&gt;&lt;b class=&#34;avatar&#34;&gt;Duck:&lt;/b&gt; Good day, Tortoise.&lt;/p&gt;
&lt;/div&gt;
</description>
    </item>
    
  </channel>
</rss>