Modern frontier LLMs can still be used as rubber ducks, and it's a great.

Check out their docs for a glimpse: https://elevenlabs.io/docs/api-reference/introduction

If you wanna hook up a voice agent to Twilio for support for example, 11labs is probably one of the quickest and least painful ways to integrate while still maintaining control over your agent and behaviors.

Yes you can vibe code your own glue code, but try that in a large enterprise where you have to consider your team now taking on perpetual maintenance; and not having a vendor/SLA to just send tickets to when something breaks (or you want something new).

Heck, since Codex is open source, you can just maintain your own personal fork with the things you like (and the things you don't like disabled). Sol is pretty good at keeping you up to date with upstream.

My Codex fork even exposes an OpenAI-compatible API endpoint; all using my subscription.

Deepseek is usually very good with open weights, they don't necessarily drop immediately, sometimes in a few hours, sometimes in a couple days.

I've been using it via openrouter pretty heavily as my daily driver for the past week and loving it, have never experienced incoherent rubbish even at 500k+ contexts (that's usually way higher than I'd typically compact at), and tool calling reliability is better than Opus 5 in the Claude Code harness.

Modern Anthropic models frequently get tool calls wrong, invent non-existent references or SQL tables, or have gibberish CJK characters in the output, like out of nowhere. Of course, they're great at self-recovery after an incorrect tool call, but so is Deepseek v4 flash.

If you're running a quant, and esp with a quant'd KV cache, then yeah, not surprised if you're getting incoherent results; but you're not running the real/full model.

Also, which harness? Try something like Pi or OMP. Models perform better in these harnesses than Claude Code: https://www.databricks.com/blog/benchmarking-coding-agents-d...

The main reason to use Cladue Code is a subsidised Anthropic subscription. If you're on API rates, you should not use Claude Code; you pay more for worse results. Claude Code is sadly quite bloated these days, and comes with a lot of proprietary context window garage like claude design skills, claude.ai artifacts, etc that you probably don't use, and if you do, well, you can add it.

For what it’s worth, dashcam footage can absolutely be copyrightable.

The ruling is more about “only humans can get copyright protection”, not so much anything about whether a button is pressed or not.

While your premise holds for happy cases, when you do have a cascading series of outages, not using exponential backoff is just adding a self-inflicted DoS to when you do go down.

I don’t really follow your premise and can’t really articulate many cases for when you shouldn’t use exponential backoff. Maybe if you’re working at Jane St or something; or other circumstances where you can deploy immediate changes to the client; and you’re willing to trade ‘better p50 for worse outages’.

But in the case of shipped code that’s run on clients, I’ll continue exponentially backing off all the way, all the time, for everything.

I hypothesize it partially explains why Claude's writing gets more Claudish with almost every model release.

Most MoE architectures have a few experts that are always running; this, the router, KV, and whatever else you have space for can stay in fast VRAM; and the remaining experts can be offloaded.

Also, you don't need to mark up tokens much if you're a commodity volume business. Think of Costco and their margins & membership fees. Not everything has to be high margin, not everything has to be a SaaS subscription.

There may be trademark infringement when you use another company's trademarks. There are some exceptions, for example copy like 'Compatible with $X' or 'Learn why users are switching from $X to ' are generally fine. The line has been drawn over decades of court battles and case law.

At work, we've dealt with a few examples that go as far as falsely impersonating our brand.

Recently, we've started getting 'explanations' from these (usually fly-by-night operators) that it was 'unintended' and the result of AI targeting and optimization. Yeah, right.

Probably why they disabled it.

Cerebras is a B2B hardware company. It feels like a distraction: think of the opportunity cost, and resources/headcount not working on other things that would drive more impact.

Should NVIDIA do a coding subscription too? I'm sure they can make money off it, but I think it would be -EV.

OpenAI's Sol ultrafast (powered by Cerebras) is still in preview, presumably because they're overall capacity bound.

They do not seem to discount cached input for the self-serve Developer tier. Maybe they do for enterprise rate cards?

https://inference-docs.cerebras.ai/capabilities/prompt-cachi...

The app is still available in Russia on both App Store and Play Store.

[1] https://blog.google/company-news/inside-google/company-annou...

Or, a webcam for example, or other peripherals.