|
|
Subscribe / Log in / New account

Define “prompt”

Define “prompt”

Posted Oct 16, 2025 11:48 UTC (Thu) by iabervon (subscriber, #722)
In reply to: Define “prompt” by Wol
Parent article: The FSF considers large language models

I've been finding that typing the explanation like I was talking to coworkers in a group chat works just as well as saying it out loud, and putting it in a version-controlled file that I clear out before making a pull request often results in having some great phrasing to use in the documentation or commit message, even though the original form would be useless in organization outside of an unfinished topic branch. This also results in some great information when I come back to a preempted project a few months later and want to know what I said to the duck when I was working on it.

Of course, it means I have a file in version control which says that it's a list of explanations of the issues I'm facing with features in progress, and then doesn't have anything else in any mainline commit.


to post comments

Define “prompt”

Posted Oct 16, 2025 16:04 UTC (Thu) by SLi (subscriber, #53131) [Link]

I agree. Often even better when you put some time into it.

But I think writing clearly in a non-dialog setting is a skill that perhaps even most engineers lack. I think all engineers should be taught technical writing (I know my university didn't for me). Many don't even seem to realize it's a rather different skill set.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds