1,646 karma · joined February 14, 2022
Get in touch at hello@tombedor.dev, or at https://x.com/middleagedc0der
That sounds... fine?
If I want to switch from Windows to Linux, I have to reconsider a whole variety of applications, learn a different UX, migrate data, all sorts of annoyances.
When I switch between Codex and Claude Code, there is literally no difference in how I interact with them. They and a number of other competitors are drop in replacements for each other.
I wrote about it here: https://tombedor.dev/open-source-models/
A) it would be impossible to find in a sea of AI generated slop
B) even if it were to be recognized as good, it would be instantly copied by other AI’s such that it would be very shortly thereafter be also considered slop
For any work to gain traction with an audience, there needs to be scarcity. Art and artists are valued because they are unique in some way, something about it or them cannot be replicated by others. The ability to instantly produce a piece of “art” negates any artistic value, at least as far as audiences are concerned.
I hate to be a "source?" guy, but I'm curious if you have any examples of this. Skills and MCP are really the only extensions on CC itself I'm aware of, and these are both supported in Codex.
Things like Dispatch / remote sessions is something CC has that Codex does not, but these features are quite easy to replicate (and I expect Codex to do so in short order).
This week I’ve been hitting CC rate limits, and I switched to Codex with virtually no disruption to my workflow. It’s not good for Anthropic that I was able to do that!
I’ve been primarily on Claude for the last 6 months or so, but have been hitting rate limits. I switched work to Codex seamlessly, just like I could switch to any other provider seamlessly
Even accepting this, how exactly are these peaceful, western friendly civilians going to withstand a war better than their country's army?
It's very depressing to see this playbook credulously trotted out yet again. When has this worked?
This is no longer necessary to inflict the catastrophic destruction we're really referring to when talking about a hypothetical WWIII
Because they are really, really well designed for humans.
Everyone is trying to reinvent the wheel and create "agent interfaces", but there is fundamentally no difference between what makes a text based interface easy for a human to use and what makes it easy for an agent to use.
"Local" is the means to an end, not the value prop itself. The value prop is "fast, private, and free", which I think is going to be very compelling.
Not an outcome I'm eager to see!
I really think art (as in art that’s made for it’s own sake, as opposed to jazzing up a PowerPoint slide or whatever) is by definition something AI will not make inroads in
Ford invested heavily in an in-house, highly optimized production pathway for the Model T. Other manufacturers sourced a lot of their parts from vendors.
This gave the Model T a great advantage at first, but they had a lot more trouble than competitors in coming up with new models. Ford ended up converging with the rest of the industry in sourcing more of their parts externally.
The lack of new Tesla models makes me feel like a similar pivot is what Tesla needs. My suspicion is that they probably need a less terminally distracted Musk to pull it off.
For example, I have it ignore messages about code freezes, because that's a policy question that probably changes over time, and I have it ignore urgent oncall messages, because the asker there probably wants a quick response from a human.
But there's a lot of questions in the vein of "How do I write a query for {results my service emits}", how does this feature work, where automation can handle a lot (and provide more complete answers than a human can off the top of their head)
Inconsistencies also pop up in backtesting, for example if there's a point that the llm answers different ways in multiple iterations, that's a good candidate to improve docs on.
Similar to a coworker's work, there's a certain amount of trust in the competency involved.
It's been especially helpful in explaining and understanding arcane bits of legacy code behavior my users ask about. I trigger Claude to examine the code and figure out how the feature works, then tell it to update the documentation accordingly.