I have done this for all my work this week and it works quite well.
For one it lets you actually query the LLM as to why, their plans give a high level not every single change and it allows you to correct it as you go and the plan will change.
1,565 karma · joined November 27, 2016
I have done this for all my work this week and it works quite well.
For one it lets you actually query the LLM as to why, their plans give a high level not every single change and it allows you to correct it as you go and the plan will change.
go lang has a scanner [0] which only shows issues when the code actually calls the effected functions.
It might be called grok out it was trained by the composer team using a large chunk of their training data.
In agent mode it’s horrible for editing files etc but better if you are juggling multiple chats
they noted in their blog post they didn't focus purely on coding for grok 4.5.
I think that’s the real point the article’s making. Unless you already know the ropes, you can’t tell if a plan is actually any good. I use LLMs all the time for work, but only because I get the system well enough to spot the nonsense or catch when a plan duplicates something that already exists. They really do keep rewriting the same functions over and over in the code.
at least codex and grok are open source so we can see what is going on.
My two guesses would be one the LLM decided it needed these files for the task or two the user simple asked grok to do it so they could post the tool calls on twitter.
If the evs end up generating a tonne of material that we can’t do anything with that would be a short term gain.
My question that once you mined the materials for the car + battery, shipped that somewhere to be built, then shipped that to be sold.
Then you have the added waste battery once it not longer hold enough charge. Is it actually better for the environment?
If we add all this extra pull on the grid we need to generate the power for that too.
They knew exactly how developers worked from using figma as training data.
disagree, then you end up with something this this
function checkAll(target, conditions) { return Object.entries(conditions).every(([path, expected]) => { const value = path.split('.').reduce((o, k) => o?.[k], target); return typeof expected === 'function' ? expected(value, target) : value === expected; }); }
and const ok = checkAll({ user, account }, { 'user.isActive': true, 'user.isSuspended': false, 'account.status': 'open', 'user': u => u.hasPermission('read'), // predicate for the trickier bit });
how is that better?
but suddenly because its a screen suddenly that responsibility to parent goes away?
i'm not trying to provoke I simple don't understand the other side of the argument.
It then has to look over everything see how it connects together and then decide the best way to do something.
Giving it small and very focused plans when you already understand the system gets it done fast and cheap.