As long as they think these leopards won’t eat their faces, that is.

Ads of you wearing the clothes they are trying to sell you. Yet another torment nexus to build!

“Don’t Create the Torment Nexus” in this case is Stand on Zanzibar from 1968, which called this concept Mr and Mrs Everywhere

I have my doubts this would ever catch on, people will be creeped out and furious for ads (generally speaking), perhaps online clothing shops previewing is palatable

White listing doesn’t protect against supply chain attacks. You need some sort of behavioral analysis.

What the industry is discovering is that copywriting is actually a skill. And it becomes pretty obvious if you don’t have any of it.

All security is a negotiation of allocating resources. It always ends with “well, that’s good enough for this.” There is never a “Ahhhh we’re done!” It can always be “more secure”.

The scorpion shrugged, and did a little jig on the drownings frog's back.

"I could not help myself. It is my nature."

Then they both sank into the muddy waters of the swiftly flowing river.

It’s not just hackers - since legitimate sites block AI crawlers, the AI are just grabbing whatever will let them read anything - killing legit sites and feeding slop farms and feeding misinformation! The future is so bright!

It was better when they had gemma at 1k. Inco does DS flash at about 600. A few places will do K3 and GLM in the hundreds.

Such a tiny model at that t/s is less impressive than it would have been four months ago.

Lighting my codebase on fire at the speed of light. Like microwaving the spaghetti.

I genuinly only see these speeds being useful for customer service/transactional workflows. Of which much smaller models can do the job (but those dont make tons of money for companies like Cerebras that need to pay off massive amounts of debt).

Nobody needs to code at 600 words per second. Using a 100tps model for an hour or so will leave you with 4-8hrs of code review and revision work.

Human code review? What is this, 2025? The modality today is write with one LLM, review by a different one, (important: two different model families will catch errors one series won't) then deploy right to production.

> then deploy right to production

And when things go south, you blame AI?

I would be very curious to see how you explain it to your customers.

Is it going to sound similar to this?

> You see, our well-meaning AI-generated code has caused all your data to be permanently deleted. In case you are confused as to who to blame, we would like to clarify that we did not write, nor review the code. So we cannot possibly bear any responsibility for its mistakes. The responsibility lies with the LLMs, not us. We have already fired the LLM which did the coding and the review. And we are already using their main competitors. Hopefully that settles your concern with the quality of our service and we are looking to have you on board of our next products.

> And when things go south, you blame AI?

This seems to work well enough for people who deploy cloud instances without redundancy to us-east-1 then blame AWS when there's an outage. I say this somewhat unironically because if one pushes the "move fast and break things" slider all the way to the right then they're necessarily assuming that type of risk. Of course some people will try to have their cake and eat it too [1] as regards velocity and quality but that's a separate discussion.

[1] I've never understood this idiom because if one isn't in possession of their cake before eating it then they're eating stolen cake which is a decidedly anti-social activity and orthogonal to the point of the saying. It should be "eat their cake and keep it too" or something.

Yeah, idk. I work on serious things. Thats not how I do things. Not everything is webdev hobby projects. There's basically no instance where offloading your code review to an llm is acceptable behavior, except maybe for a one off tool you need personally.

And if you tell the reviewer the author is a competitors model it becomes extra snarky and vigilant. Then give the review results to the author and tell it it's from the competition and it will also become slightly outraged.

No you dont need to code at 600 w/s BUT at those speeds, you can start doing things like asking multiple different agents the same question and picking the best solution each time without noticing the lag.

So 3x the code review lol. This is similar in concept to how a slot machine leta you choose 1x, 3x 6x lol

> Nobody needs to code at 600 words per second.

I do. I used to use haiku for the speed. Now its just as slow as the rest. Speed is my #1 ranking of how good a model is

I prefer a fast model too, but you cannot get more done just because its faster. You just get to the human parts a bit faster. Code review, revision ect.

absolutely not ! it's not an "ohhh ill get 100x more coding done" it's definitely a preference/work style thing. I find it's hard to get in "the flow" when managing multiple agents, and if I just do one at a time with today's frontier models, I find myself waiting 10 minutes twiddling my thumbs while they do something all the time. Then needing to catch myself and turn back over to it when its done, all these micro switches between tasks is really difficult for me. If I had an instant agent I probably would be somewhat faster, but not zomg1000xunicornrockstar nonsense. I would be way happier though

I don't even notice the LLM speed or latency. I think we are as far apart in technique as it gets.

What is your workflow?

Inco sucks. I tried their GLM 5.3 Flash and it was quantized to the point of hallucinating Chinese in the middle of English only agentic sessions. Never happened with any other provider.

In the world of protein low carb pop tarts juice is poison.

How hard is it to find some high-protein fruit juice these days?

Given that there's no strong regulation that forces fruit juice to be made from fruit, I'd wager that this is already a product line.

"Contains 0% Juice"

you can't call it juice if there's no juice

That ceiling set in… June. Yes. Slowing down for sure.