Conversation

Notices

1. Embed this notice
   Pete Alex Harris🦡🕸️🌲/∞🪐∫ (petealexharris@mastodon.scot)'s status on Friday, 06-Feb-2026 20:00:28 JST Pete Alex Harris🦡🕸️🌲/∞🪐∫

   • Michael Miller :blobrdm: 🦆
   • Dave Rahardja
   • your auntifa liza 🇵🇷 🦛 🦦
   • Anthony 🇦🇺🦘🐨🪃🌟✨️🕯🏏🧩🎭🪁

   @raineer @drahardja @skyfire747 @nomenloony @blogdiva

   Domain expert here: they aren't extremely effective for me in my field (programming) because to tell an LLM precisely enough what to do, I'd have to use a verbose English description, and I've already constructed the solution in my head in a more structural form that isn't words. Turning it back into words to tell an LLM what code to generate is a step backwards.

   • Embed this notice
     Matt Hardy 3.11 for Workgroups (technicaladept@techhub.social)'s status on Friday, 06-Feb-2026 20:00:27 JST Matt Hardy 3.11 for Workgroups

     in reply to

     • Michael Miller :blobrdm: 🦆
     • Dave Rahardja
     • your auntifa liza 🇵🇷 🦛 🦦
     • Anthony 🇦🇺🦘🐨🪃🌟✨️🕯🏏🧩🎭🪁

     @petealexharris @raineer @drahardja @skyfire747 @nomenloony @blogdiva Don't you do that anyway when you add comments to your code?

     Rich Felker repeated this.
   • Embed this notice
     Pete Alex Harris🦡🕸️🌲/∞🪐∫ (petealexharris@mastodon.scot)'s status on Friday, 06-Feb-2026 20:00:27 JST Pete Alex Harris🦡🕸️🌲/∞🪐∫

     in reply to

     • Michael Miller :blobrdm: 🦆
     • Dave Rahardja
     • your auntifa liza 🇵🇷 🦛 🦦
     • Anthony 🇦🇺🦘🐨🪃🌟✨️🕯🏏🧩🎭🪁
     • Matt Hardy 3.11 for Workgroups

     @technicaladept @raineer @drahardja @skyfire747 @nomenloony @blogdiva

     No, a duplicate explanation of what the code is doing is not what comments are for.

     Comments are more for "why" one method or choice than another, sometimes "why not", than "what".

     Except doc comments, which are closer to spec i.e. "what". The code itself is "how", and it doesn't necessarily come via a verbal description in natural language.