Symon Baikov

@symonbaikov.bsky.social

Full-Stack Engineer | SaaS, Automation & API Systems | React, Node.js, TypeScript

In a study of 400,000 Claude Code sessions, Anthropic found that domain expertise, rather than programming ability, is the primary factor in effective autonomous AI work. Success rates converged across different professional fields, suggesting that agentic coding enhances existing expertise.

地味に効くんですよね、これ。同じプロンプトを1日に何十回も投げてると、トークン消費が2倍近くになってる気がする。 レスポンスをキーにしてローカルにキャッシュしておくだけで、API費用が実測40〜50%落ちます。実装は辞書1つ、5行のコードで完了。 Just cache identical prompts locally — costs drop 40-50% in practice. One dict, 5 lines of code, done. #AI #APIコスト削減 #ChatGPT #LLM #Prompting #キャッシュ #AI自動化 #TechT…

isoAi 生成インフォグラフィック: API料金を半額にする最小限のキャッシュ術

42% of companies scrapped AI projects last year (up from 17%). Not a tech problem. A measurement problem. Only 18% of orgs track ROI on AI spend. The other 82% fly blind — then act surprised when budgets vanish. 1,400+ sessions. Every metric published. Unmeasured AI fails.

any-llm-gateway adds production controls on top of any-llm: • Shared budgets with scheduled resets • Virtual API keys with metadata and expiration • Token and cost tracking per request • Docker-based deployment with Kubernetes-ready probes Try it out: link.mozilla.ai/any-llm-gate...

Bild

CC has native subagents now — a .claude/agents/*.md manifest with its own description + tool scope, invoked by the orchestrator via the Task tool. No MCP needed. The win is scoping each subagent's tools tightly so the orchestrator's context stays clean.

To be clear, I’m in no way defending AI usage, I just feel like I’m in an anomaly team that uses it but with a shitload if guardrails and caution. Everything still gets full code review, it’s never allowed to commit code independently on core systems, we all have decades of coding experience…

Two weeks bolting more tools onto my coding agent. The 12th didn't help. It slowed planning and made the agent misroute on easy tasks. Trimmed back to 6 sharp ones. ~30% faster, picks the right tool first try. Tools are a budget, not a buffet. #claudecode #ai #aiengineering #buildinpublic

When I was Lead Product Architect at Workday, I saw teams adopt tools based on vendor demos and then spend months debugging edge cases the demo never showed. Think about what that means for AI model adoption. "It benchmarks well" is not an integration test.

Gartner: 40% of enterprises will decommission AI agents by 2027. Not because agents fail — because governance was wrong. Uniform governance is the failure mode. Govern by architecture (what the agent can reach), not instruction (what it's told). 1,413 sessions. Still running.

sounds good! i've got a little dashboard where i can dispatch review agents with custom instructions, effort configs, etc. and an mcp method they call when they're done. and a private gitea instance, so i don't have to reinvent what a code review is and i get a human readable interface to it

I've been doing something similar albeit with a single model (claude opus). 1. Determine review targets: testing, observability, business requirements, security, rollout risk, etc. 2. Spin up two agent teams: blue (prove it works) and red (adversarial review) 3. Loop until red+blue say it passes

Of friends who use coding agents heavily, the happiest seem to fall into two camps: a) Controlled: 1-2min cycles, no context switching, still in control of the code, using the agent "to type faster" b) Delegated: Vibed in the background, while something else (eg design) is their primary focus

x.com

This week in AI Dev: the US export order that pulled Claude Fable 5 + Mythos 5, SpaceX’s $60B Cursor buy, Zhipu GLM 5.2, Moonshot’s Kimi K2.7-Code, Vercel Eve, Agentjacking, Databricks OpenSharing, Google’s Antigravity CLI, and Anthropic’s paused Agent SDK billing. www.everydev.ai/p/news-week...

Weekly AI Dev News Digest: June 13 - June 19, 2026 | EveryDev.ai News

A US government order pulled the most capable coding model on the market and kept it offline for a week, with no developer outside Anthropic able to…

everydev.ai

This is the real blocker most teams hit—agents without context just shuffle tickets around. The question is whether you're building this as a general MCP or optimizing specifically for how MSPs actually triage and escalate, because that workflow is weirdly specific.

The best site on the internet for Harness Engineering, completely free. The better the harness, the better the agent. AI coding agents are powerful but without the right controls. > they can be inconsistent > make mistakes > struggle with larger tasks That is where Harness Engineering comes in.

Bild

What Dhinakaran gets RIGHT about where harnesses came from: They emerged bottom-up from production coding agents like Cursor, Claude Code, and Windsurf. The pattern was discovered, not invented. Nobody sat in a room and designed the 9 components. Production pressure forced them into existence.

deepmind's real concern: when millions of AI agents interact unsupervised, your data governance infrastructure breaks. not from bad actors. from cascading effects you can't observe. build observability now. #AI #DataStrategy #DataEngineering

🤖 Why Amazon, Uber, and Meta Are Quietly Curbing Their AI Use (Hint: It's Not About Performance) AI's hidden compute costs are shocking CFOs and forcing budget cuts at major companies. https://theneuralfeed.com/share/post/eITTv1AI #AINews #TechNews Read the full story →

theneuralfeed.com

webmcp in chrome 149 origin trials = agents can call your functions directly instead of hitting expensive apis. control the contract, cut the cost, own the audit trail. worth testing if you're running ai agents. #AI #DataEngineering #DataStrategy