| ▲ | shmatt 3 days ago |
| in the beginning i was agitated by Concise and would move it back manually. But then I actually tried it, I asked for SQL and it gave me back SQL and 1-2 sentences at most Regular mode gives SQL and entire paragraphs before and after it. Not even helpful paragraphs, just rambling about nothing and suggesting what my next prompt should be Now I love concise mode, it doesn't skimp on the meat, just the fluff. Now my problem is, concise only shows up during load. Right now I can't choose it even if i wanted to |
|
| ▲ | cruffle_duffle 3 days ago | parent | next [-] |
| Totally agree. I wish there was a similar option on ChatGPT. These things are seemingly trained to absolutely love blathering on. And all that blathering eats into their precious context window with tons of repetition and little new information. |
| |
| ▲ | therein 3 days ago | parent [-] | | Oh you are asking for a 2 line change? Here is the whole file we have been working on with a preamble and closing remarks, enjoy checking to see if I actually made the change I am referring to in my closing remarks and my condolences if our files have diverged. | | |
| ▲ | cruffle_duffle 3 days ago | parent [-] | | You know the craziest thing I’ve seen ChatGPT do is claim to have made a change to my terraform code acting all “ohh here is some changes to reflect all the things you commented on” and all it did was change the comments. It’s very bizarre when it rewrites the exact same code a second or third time and for some reason decides to change the comments. The comments will have the same meaning but will be slightly different wording. I think this behavior is an interesting window into how large language models work. For whatever reason, despite unchanging repetition, the context window changed just enough it output a statistically similar comment at that juncture. Like all the rest of the code it wrote out was statistically pointing the exact same way but there was just enough variance in how to write the comment it went down a different path in its neural network. And then when it was done with that path it went right back down the “straight line” for the code part. Pretty wild, these things are. | | |
| ▲ | pertymcpert 3 days ago | parent | next [-] | | I don't think the context window has to change for that to happen. The LLMs don't just pick the most likely next token, it's sampled from the distribution of possible tokens so on repeat runs you can get different results. | |
| ▲ | dimitri-vs 3 days ago | parent | prev [-] | | Probably an overcorrection from when people were complaining very vocally about ChatGPT being "lazy" and not providing all the code. FWIW I've seen Claude do the same thing when asked do debug something it obviously did not know how to fix it would just repeatedly refactor the same sections of code and making changes to comments. | | |
| ▲ | cruffle_duffle 3 days ago | parent [-] | | I feel like “all the code” and “only the changes” needs to be an actual per chat option. Sometimes you want the changes sometimes you want all the code and it is annoying because it always seems to decide it’s gonna do the opposite of what you wanted… meaning another correction and thus wasted tokens and context. And even worse it pollutes your scroll back with noise. |
|
|
|
|
|
| ▲ | nmfisher 3 days ago | parent | prev [-] |
| Agree, concise mode is much better for code. I don’t need you to restate the request or summarize what you did. Just give me the damn code. |
| |
| ▲ | johnisgood 3 days ago | parent [-] | | An alternative way to the Concise mode would be to add that (or those) sentence(s) yourself, I personally tell it to not give me the code at all at times, and at another times I want the code only, and so forth. You could add these sentences as project instructions, for example, too. |
|
