Whatever you're doing, try doing 500 or 1,000 of it in a batch. You'll exhaust any subscription quota you have, or if you're paying per token, you will probably find it too expensive. That's when you'll start to ask "how smart a model do I really need for this job?", and you'll investigate running a small but sufficiently capable model on your own PC, churning overnight through your 1,000 tasks.
Concrete: Last year I was DIYing a solar-power system for my home. I spent about an hour spitting out a Python tool that took (as inputs) drone photos and JSON and generated several proposed roof layouts for the panels and conduit. The tool helped me identify the exact railing attachment points and route around existing roof obstructions. Professionals already have these tools, and maybe they're available to DIYers, but you know what? It was faster to build my own than to do the product research on the web.
Abstract: This "oh shit" was more of a slow burn than a sudden realization. I see a lot of angst from developers who complain about their LLM agents. Agents write terrible code that barely works. They say things are done when they aren't. They misinterpret feature requests and ignore clear-cut project rules. They make assumptions that would have taken three seconds to research and invalidate. They suddenly quit because we're not paying them enough. And so on.
But you know what? All those complaints apply to humans, too! The industry has been dealing with these problems forever. Many of the same management techniques and software-development processes apply. This is why I discount a certain class of criticism about AI-generated code. If a fault of an LLM applies equally well to human engineers, and the person voicing the criticism hasn't managed a team, then I'd invite that person to wear a management hat for a while. Read some books/blogs, talk to an EM. Maybe this is a skill issue, which matters because we're all managers now.
The "oh shit" for me is that I have yet to hear a criticism that I can't map to one or more actual engineers I've worked with -- eventually successfully -- in my career. Which means that I'm still waiting for a new criticism, and eventually absence of evidence might be evidence of absence. LLMs fit too well into the giant machine of commercial software development for them to be a parlor trick.
Everyone but me might be a philosophical zombie. But I still treat them with respect. I do this because I like living in a world that gives us the benefit of that doubt.
It can't hurt to say "please" and "thank you" to an LLM.
Doesn't 91.3(a) already give the PIC absolute authority to act regardless of whether there's a threat? Why invoke the FBI?
> Turning the plane around and landing is certainly in the realm of "reasonable".
Agreed. But doing it without the FBI threat would also be in the realm of reasonable. Which, it could be argued, means that making the FBI threat was unreasonable, or at least very close to it.
Retired manager, been in my share of tense meetings.
I appreciate it when someone recognizes that they're struggling with conflict and emotion, and lets me know that they know this. It's better to acknowledge the emotion and put it on the table as its own valid topic of discussion, than to tiptoe around it or try the "I'm sensing that you're dealing with some internal conflict" approach that risks embarrassing them or worsening it.
The choice is whether to acknowledge the emotion, not whether to have it.
If you believe there will be lots of LLM providers in the future, then OpenRouter could be a DoorDash play.
Established restaurants didn't need DoorDash because they were already on everyone's speed dial. But new or small restaurants couldn't afford to advertise or maintain a team of delivery people. DoorDash created a two-sided marketplace that made it a lot easier for new entrants to bootstrap. Today even the established restaurants have to pay them their tithe because hungry people have learned to start with the DoorDash app. A bit of a prisoner's dilemma.
If OpenRouter plays its cards right and gets very lucky, a large number of people will configure their hungry LLM clients to start with OpenRouter, and then LLM providers will have to join the marketplace or else miss out on all those customers.
not sure that works as well when they don't own their API though; how much software is openrouter-only in a way that's not 5min of deepseek to patch the source for, or 15min of opus to patch the binary instead
I agree that technical lock-in wouldn't cause the consolidation. Instead, if it happened, it would be because of the network effects of the two-sided platform.
People could email cat photos and resumes. But Facebook and LinkedIn are where everyone already is, so that's what they use instead.
Everyone (except Anthropic) seems to be settling on the same API, so nobody "owns it" anymore. I expect there to be practically no software that's OpenRouter-only.
reply