Hacker News new | ask | show | jobs
by H8crilA 644 days ago
Why not just ask the bot to do something? I'm using it daily and don't have to spend more than 5 seconds thinking of a "prompt".

The only exception is function calling (or whatever they call structured output these days), but that is simply embedded in my or other people's programs that call the API.

3 comments

This is what I've found effective.

I use conversational English for basically every prompt I work with ChatGPT on as a regular person.

For my application, I have prompts that I have stored in source code, but those need to have very consistent, exact inputs and outputs (mostly JSON), so creating a specific prompt is important for those.

For anything human where a human can parse it, regular ChatGPT works perfectly fine!

I think you guys are responding to the title, not the question. OP is wondering how to organize the history of chats.
This is true, and you're right. I think the perspective we're trying to walk from is: "if you're creating custom queries just to find common things from ChatGPT - that is, you're not creating an assistant and you're not using it for a coding backend (which have their own solutions), then we don't recommend going that route and going a different route.

What I've said does smell of the Super Smart(tm) and completely unhelpful Stack Overflow response, I will give you that.

I made a private blog that if something seems really valuable, I blog the prompt and output. Private so I don't waste time on the delusion of someone else reading it and everything that comes with that time wise.

Beyond that, the previous chats could practically be deleted for me. Its not like my prompts are such works of art that I couldn't recreate the thought if needed. Not to mention, Sonnet has made me not use chatGPT for about a month now so the blog is nicely divorced from the LLM flavor.

I asked it for a solution and it told me to export the data and use a search indexer like typesense / InstantSearch.
It depends how often you do a thing. It's ok to write things from scratch a few times. But if you often ask about the same database which involves dumping a long schema and including extra context for the information in it, you don't want to write it more than once. Or if you often ask for specific things like visualisation of data, but you don't want to manually explain each time that you want to use polars and pyplot and typed python and get timing around longer running functions and ...

If you're doing ad-hoc things, yeah, just ask. If not, prompt management saves lots of time.