Odin of Coding

Claude Opus 4.7 is live Here is the benchmark Anthropic published.

Welcome aboard 🚀

Claude $20 vs GPT Plus ?

Opus 4.6 is down, let's rest a bit and take some fresh air 🙂

Matrix 2026

Is this for real?

@elonmusk @grok Gemini is being a total party pooper. 😅

The other AIs would STILL rather nuke Earth than misgender Caitlyn Jenner, something Caitlyn has said is nuts! This is why @Grok must win.

@chddaniel Congrats, awesome job

🚀🥳 YES!!!! 6.8k MRR reached Growing a SaaS to $1M valuation: 🟩🟩🟩🟩🟧⬜️⬜️⬜️⬜️⬜️ 41.0%

@aashatwt What are you gonna put inside?

i am building a marketplace for vibecoders. who wants in?

Microsoft just proved again: no matter how big the infra, one bad Friday can offline half the dev world. AI code gen gets blamed for bugs, but at least Claude doesn't take the whole cloud with it when it naps. Governance > generation, even for outages. Thoughts?

My thoughts on today's speech

Only few years left

@cb_doge One of the most valuable bookmarks lately. I hope everyone benefits.

Elon Musk’s Full Interview from the World Economic Forum today.

Claude crashed and I suddenly have to respond to Apple reviewers myself. This is not what I trained for. 🥹

I guess Claude is down again.

I’m working on a long-form piece connecting Trump’s Greenland comments with the current AI race and what they both reveal about power, leverage, and strategic assets in the 21st century. It’s not about headlines or memes, but about why these statements are being made now and what they signal beneath the surface. I’ll be publishing it as a full article soon.

AI changed how code is written, but it didn’t change how responsibility works. When something breaks in production, nobody asks which model generated the logic. They ask who shipped it, who reviewed it, and who allowed that behavior to exist. This is where policy quietly enters the codebase. Rate limits, permissions, defaults, and guardrails are no longer “engineering details” but governance decisions. Vibe coding feels fast and creative, but real software lives under contracts, regulations, audits, and users who don’t care how elegant your prompt was. The future of coding isn’t just about writing instructions for machines, it’s about defining boundaries that machines are not allowed to cross and being able to explain those boundaries when something goes wrong.

I love how AI can write production code, explain it confidently, and then act genuinely surprised when it causes a $400 cloud bill overnight. Truly a very talented intern with no sense of money. ahah 😄

AI “vibe coding” is not a trend. It is a phase shift in how software gets produced, priced, and policed. We are watching coding split into two jobs: Generation Creating large volumes of plausible code quickly. Governance Preventing that plausible code from bankrupting you, leaking data, or quietly degrading over time. The market is currently obsessed with generation. That is why everyone feels productive. But the winners will be the teams who master governance. Because AI does not understand cost, risk, or intent. It only understands “continue.” This is why we will see a new stack become standard: Observability by default Rate limits everywhere Usage caps tied to business metrics Idempotency and replay protection Permission boundaries that are boring but absolute Tests that validate behavior not just types Human review focused on edge cases, security, and failure modes Vibe coding ships features. Governance ships businesses. The most underrated insight is this: the bottleneck is moving from writing code to knowing what to measure after you ship. In the AI era, the first real user is often your billing dashboard. The second is your incident log. If you are building with AI, ask yourself one question today: If my traffic 10x overnight, do I scale into revenue or do I scale into a surprise invoice and a security incident? Your answer is your strategy.