Code review, qa, staging, product review, dog fooding… what do you mean “now”? It’s always been all of our jobs to catch all of our errors. We’re just including the AI’s errors now hoping that the overlap of everyone’s errors is sufficiently small.
But in all seriousness, the KLR is such a great example of this mindset. Find the tool that suits your needs, learn how it works and how to maintain it, and you're set for life.
Not really - fine tuning can be done on much lower tier hardware, with much smaller datasets. With a model like Qwen 3.8 27B as the core, a small fleet of LoRA adapters for whatever specific use cases you need would be incredibly competitive with the current frontier. Sure, future frontier models will likely continue to improve, but will people need them for everyday usage? I'd wager not. Unfortunately, my wager is dwarfed by OpenAI's and Anthropic's.
I know this sounds ridiculous, but try fine tuning a small local shell -> plain language model, then using the output of that for whatever you need on your end. You'll get the gist of what the frontier model is trying to accomplish, and can handle it with whatever harness workflow you want.
I'm not sure I follow, can you expand? Why would I want to go from shell to plain language? I don't have a use for an explanation of the shell command that I am aware of. I do sometimes enable a policy-tuned llm to add a non-deterministic check, especially when they try that "command didn't work, let me put it in a script and run that"
If this is in relation to removing the need for shell, my idea is more like inspecting common files like Makefile or package.json to extract and dynamically generate tools for the llm call.
Pinned at the front and back on a rotating axis down the centreline of the car, with the "car" itself being mostly lightweight composite with zero internal components other than the necessary air tanks and a large RC car motor to get it to roll up to the jump point? For the support structure, just put some dark matte scaffolding in the background so it stays out of shot and hidden by the light show. It wouldn't be too far off from standard wirework for movie stunts, and the compressed air could still do enough work to fool the eye. It's not like people have an innate sense for what a gas thruster powered flying car should look like anyway.
I don’t think that would work here where you have to support a 170 degree y axis rotation and then a 180 degree x axis rotation with a wall on one side. I think it would work for the jumping the semi demo though!
They were aiming for better concurrency, I believe. If you're rewriting something regardless, might as well use a more modern language that's easier to reason about during development.
Did you read the article? Meta themselves aren't confident that what they're doing is legal, and they're very clear about the fact that it might be clawed back by the IRS because they're abusing a tax credit intended to be used for experimental research by putting their massive data centre build out into that "experimental research" bucket.
If a company's accountants and lawyers are concerned enough to bury disclosures in their securities filings to cover themselves, but the company leadership is brazen enough to proceed anyway, I'd say that's plenty of justification for people to be mad at the executive leadership.
reply