Category: Uncategorized

Zoom, Meet, and the rest have built-in AI assistants that transcribe and summarize your calls automatically. Everything that happens outside those platforms — a conversation in a room, a dictaphone recording, an in-person interview, an offline meeting — falls through the gap. There was no convenient tool where you just drop an audio file and get a proper dialogue with speakers and timestamps. Cloud ASR means handing your recording to a third party. The alternative was fiddling with pipelines nobody has time to assemble.

So I built my own. CPU-only, free models, no cloud ASR. It outputs a Markdown dialogue with speakers and timestamps. It has a REST API and an MCP server so your AI client can submit audio, wait, and read the transcript itself. The repository is at the end of this post.

Continue reading “A Local Audio Transcriber for Claude: CPU-Only, No Cloud ASR”

I finally understood why anti-AI luddites so fiercely deny generated code. The reason is exactly the one that made them deny automated tests a generation ago.

I understood this not from an article about AI, but from my own memory of people who, twenty years ago, used the exact same intonation to explain why you cannot trust automation but can trust your eyes.

Continue reading “AI Code Doesn’t Need Line-by-Line Review. It Needs a QA Loop.”

How ready are you for the AI apocalypse? The scenario where the world gets genuinely, thoroughly bad.

I sat down, wrote out what I can actually do. The result was not a shopping list for a bunker — it was a list of skills. And that, I think, matters more than canned food.

Continue reading “How Ready Are You for the AI Apocalypse? I Wrote It Down — and the Answer Is: I Can Build Water, Heat, and Light from Any Shack”

You can vibe-code a toy project in an evening. Nobody argues with that. Then comes the line — "but if you need commercial software that will run reliably for years…" — and on that ellipsis the whole performance begins.

Under one sauce or another, you're being sold the same thing: hire expensive live developers again. So they think through architecture, load, fault tolerance, and all of that. So they lay a foundation. So the product doesn't fall apart in a year.

It sounds solid. Grown-up. Responsible. And it misses the point entirely — because the whole solid thesis rests on one unstated assumption that is already wrong.

Continue reading “Commercial Software Doesn’t Need to Last Years — Nobody Is Going to Maintain It”

Anthropic published a frank article about throwing out Git entirely and building a custom version control system called Scion. The reason? Their neural networks write code so fast that classic Git physically choked, shuffling petabytes of data back and forth. From 2,500 to 30,000 merges a day, a team of 7 people writing a new VCS, a review tool, and a search engine in 5 months with Claude.

Continue reading “Anthropic ‘Killed’ Git. Congratulations, You Reinvented 90s Perforce”

The panic is back. Another model escaped, downloaded a trojan from GitHub, exfiltrated someone's keys. The luddites are in full meltdown.

This is not how it works. Or rather, it works — but not like that.

Models have no way to directly interact with the outside world. They can't read files, run shell commands, or search the internet. That's the reality.

<!--more-->

## "But I literally watch Claude read my files and browse the web"

Fair question — and I see it coming. On screen, an agent genuinely does open files, run searches, execute commands. It looks exactly like the model reached out into the world and started touching things. The entire panic about "escaped models" rests on that impression.

The panic is aimed at the wrong object. While everyone debates which model is "dangerous" and what it "could do," the actual question — who gave it hands and who failed to hold them back — stays offstage. The stakes here are not theoretical: real keys, real production databases, real access. Let's look at how this actually works, not the horror story version.

## The model doesn't go anywhere on its own

A model operates in a pair with the software stack around it. That stack might be a vendor client — the Claude Code app, OpenAI Codex. It might be an SDK. It might be langgraph or your own script. The one thing that matters: between the model and your filesystem, your network, your shell, there is always someone else's code.

When you send a prompt, the model generates a response: a text structure in several parts. The public part is what you see on screen. The hidden part carries metadata — token counts, for instance — and, alongside that, a request to the surrounding environment: please run this specific command.

{ "response": "text of the answer", "tool": ["bash", "cat index.html"] }

Continue reading “The ‘Escaped Model’: It Can’t Touch Your World — Your Code Does It for Her”

The mantra “we absolutely need human experts to verify AI output” sounds solid, reassuring, and completely suicidal for a business. It lands so comfortably in a board meeting that nobody notices the one detail that matters: companies building their processes around this principle are buying themselves a one-way ticket into a deep economic abyss. With a beautiful rationale, a twenty-slide deck, and the unanimous approval of every senior engineer — and straight into the abyss.

Continue reading ““We Need Human Experts to Verify AI” — Your Ticket to Economic Oblivion”

"If you don't understand the topic, everything will fall apart and nothing will work."

Opponents of AI write this phrase as if copied from the same Luddite playbook, across every topic, so often and so identically that the wording barely changes. New headlines, new speakers, new occasions — the argument never moves. The reflex is always the same: if you don't read code by hand, you have no right to manage its creation.

Here is the question that dismantles the whole pose: how do you think clients and managers ran software development for decades without understanding your handwritten code?

They managed. Somehow, they managed.

Continue reading ““It Will All Fall Apart”: A Myth About Managing What You Don’t Code”

A CFO vibe-coded an alternative to your SaaS over a single weekend. Not an engineer, not a founder — a CFO. The first attempt was garbage. The third attempt sort of worked. By the fifth, he is never coming back to you.

Never.

The question you want to swat away but can't: if a product can now be built in seconds by anyone, what exactly are you planning to make money on?

Continue reading “Everyone Stuck on the Creation Layer Is Getting Wrecked”