@vikramcantsingh

https://t.co/Ynbuj1QbhE

no amount of dopamine hits from vibecoding will ever come close to the dopamine hit from figuring out how to copy paste in tmux

https://t.co/UWzlWuXSGD

https://t.co/vCgKhtD2VM

Migrating from the bivouac of Opus 4.6 to Codex 5.3 the travail of switching over felt pronounced. While model commodification has been a popular thesis among folks, this process of switching models pointed to moats beyond performance. The description below is inherently anecdotal but I expect might be shared by other users. 1. Entrenched switching costs: This can be primarily ascribed to personal inertia, but I found this to be two-pronged across: (i) Skills and (ii) MCP connections I use the popular skills from skills(dot)sh, but I also have a bit of an arsenal of my personally developed skills. These skills have been iteratively improved by Claude itself over time and felt like a misfit glove when using them on Codex. Reinstating existing MCP connections on Codex was also tiresome. I also wonder if more naive users will think about making their {agent}.md file composable across different models since not doing so sets up a recursively positive feedback loop for whichever model you prefer more. I only expect these switching costs to increase as the labs focus more on capturing the end user as seen through Claude Cowork and Excel. 2. Math: Codex's mathematic rigor and intellectual honesty to the problem outperformed Opus. I found this loop useful: Codex performs initial mathematical reasoning and writes high level code logic/guidance --> Opus writes code --> Codex performs reviews 3. hazard(switch over) is decreasing: The longer I use Agent X, the lower is my probability for switching over to Agent Y. This is less true today since I value experimentation but as model performance asymptotes I expect the slope of the hazard function to decline even more sharply. Accumulated customization raises switching costs and continued usage reduces the option value of experimentation 4. More anecdotal findings: I felt Opus was quick to do tasks but often took shortcuts – from hardcoding numbers to not updating results when underlying functions changed. Codex felt a bit slower for similar small tasks that Opus performed instantly. For multi-step, longer-running tasks Codex on Extra-High thinking was phenomenal. The commodification thesis assumes models are fungible and will converge to cost-plus margins like cloud compute. However, as switching costs and lock-in become more accentuated we might see a closer resemblance to enterprise SaaS where stickiness compounds with configuration accumulation. Orchestration has its space but it seems the killer end-user products are still originating from within the labs for now.