[flagged]
Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
11–20 of 144 posts
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#12> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
The problem is that the second you suspect something is written by AI, its a pretty good signal that 50-80% of the text is empty of meaning. Maybe that will change, but LLMs are terrible and inefficient writers.
Only so much time in the day, its a quick signal to not waste anymore of it.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#13Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#14> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
Not OP but my frustrations come from it being impossible to ignore and outright distracting.
I've found the same thing showing with Claude-coded/designed front ends that overuse the same semi-monospaced fonts, Blue/Yellow/Red palette and rounded corner borders. It isn't that it is bad, but it often isn't fit for purpose.
You're right it wont change anything, but authors shouldn't be surprised when people who care about their time/attention comment on low/no effort pieces.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#15Earlier quoted context omitted.
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
The problem is that the second you suspect something is written by AI, its a pretty good signal that 50-80% of the text is empty of meaning. Maybe that will change, but LLMs are terrible and inefficient writers. Only so much time in the day, its a quick signal to not waste anymore of it.
Correct. AI == Credibility hit and it's increasing as more humans get used to feeling they are AI slop consumers, not worth the time for genuine human engagement. Human engagement costs are increasing. Amazing to read/watch.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#16> we’ve made GPT 5.6 Sol the default model powering every Ploy workspace
I would consider Luna for parts of the workload that touch actual tools. It is surprisingly capable and it runs fast.
Sol is great at talking to the human and orchestration of agent calls, but it's just too expensive to use everywhere.
You can get 5 Luna runs for the cost of 1 Sol run. Statistically speaking, going from one to five samples is a pretty big deal.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#17> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
I have a counter proposition: don't fall for this constant suggestion that LLMs are an unavoidable future would you leave the techbros alone now pretty please, relentlessly keep reminding that we still don't think it's acceptable so people don't start to think this is okay since nobody complains anymore.
I appreciate these comments, they save me time for procrastinating elsewhere.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#18> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
It's both poor substance and style, in most cases (and this case.)
Pointing out they generated it at least encourages them to write a shorter article that says what they meant.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#19[dead]
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#20[dead]