this post was submitted on 10 Dec 2023
168 points (100.0% liked)

Technology

37750 readers
214 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
168
Chat GPT Did NOT Like My Memory Test (beehaw.org)
submitted 11 months ago by millie@beehaw.org to c/technology@beehaw.org
45 comments fedilink hide all child comments
 

I was trying to do a memory test to see how far back 3.5 could recall information from previous prompts, but it really doesn't seem to like making pseudorandom seeds. 😆

you are viewing a single comment's thread
view the rest of the comments
[–] Hexarei@programming.dev 1 points 11 months ago

Well, it's terrible at factual things and counting, and even when it comes to writing code it will often hallucinate APIs and libraries that don't exist - But when given very limited-scope, specific-domain problems with enough detail and direction, I've found it to be fairly competent as a rubber ducky for programming.

So far I've found ChatGPT to be most useful for:

  1. Writing SQL. Seriously, it's fantastic at writing SQL if you tell it the relevant schema and what you're trying to achieve.
  2. Brainstorming feature flow - Tell it the different parts of a feature, ask for thoughts on how the user should be guided through the process, and it does a decent job of suggesting ideas.
  3. Generating alternative names/labels for buttons and such. "In X feature, I have a button that does Y when the user has Z. Currently I have that button labelled 'Start Y', but it feels robotic and impersonal. List 10 suggestions for what such a button could say to be more personal and friendly." and the like. My favorite was a button that was labelled "Map Incoming Data to Job Details". Wound up renaming the whole process to just "Job Ingestion" because it sounded so good.
  4. Reformatting data. Give it a data structure and tell it you want that data in some other data structure, and it is really accurate at reformatting it. I don't think I'd trust it with a huge amount of data that way, but for an unimportant one-off it was a nice time savings.