Загрузка видео...

Не удалось загрузить видео

На главную

A senior engineering team costs $500,000 a year to do what these 10 open-source repos give Claude Code for free! Running Claude Code without these repos means using maybe 20% of what it can actually do. Most repos getting hyped right now are noise. These ten were tested, the...

21,314 просмотров • 3 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Broadcom's CEO just told investors that one senior engineer with Claude Opus can do in one week what ten engineers earning $300,000 a year take three months to produce. Every engineering org in the world is running the wrong headcount math. This was not a prediction. It was a report from inside Broadcom. Hock Tan said his engineers are already using Claude Opus for engineering design and code assistance. Not experimenting with it. Using it. And the output they are getting from a single senior engineer in one week is equivalent to what a team of ten would produce over three months. Do that math slowly. Ten engineers at $300,000 a year is $3 million in annual salary. Three months of their time is $750,000 of labor. One engineer with Claude Opus produces the same result in one week. He also said something that most people in the room let slide past them. The engineers who get good at these tools do not just get faster. They get better. The designs they produce with AI assistance are probably better than what they would produce without it. That is the part nobody wants to say out loud. It was never just about speed. The ceiling on what a single engineer can produce just moved. And the teams that have not figured that out yet are spending $750,000 to do what one person with the right tools can do for a fraction of that. What do you guys think about this? (Watch the full interview at Bloomberg Live on YouTube)

Ihtesham Ali

97,288 просмотров • 3 месяцев назад

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,096 просмотров • 3 месяцев назад

THE GUY WHO WON ANTHROPIC'S HACKATHON JUST GAVE AWAY HIS ENTIRE CLAUDE CODE PLAYBOOK FOR FREE. 10 MONTHS OF WORK, ALL PUBLIC Affaan Mustafa won the Anthropic x Forum Ventures hackathon by building a full startup in 8 hours with Claude Code. Then he open-sourced the exact setup that did it. It's called Everything Claude Code, and it turns Claude from one assistant into an entire engineering team Repo: affaan-m/ecc This isn't a prompt pack. It's a system he refined over 10+ months of daily use shipping real products What's inside: A huge library of skills, dozens of specialized subagents, and ready-made commands, all working together. Each piece does one job. One subagent reviews security against OWASP standards. One optimizes memory so Claude stops forgetting earlier decisions around hour three. One learns from your past sessions and projects so the setup gets smarter the more you use it. Others handle planning, test-driven development, and language-specific code review Instead of one assistant writing code, you get an orchestrated team. A main session delegates to the right specialist when the task calls for it, the way a real dev team splits work The best part: it's not locked to one tool. It runs in Claude Code, Cursor, Codex and OpenCode, across Windows, Mac and Linux. Free, MIT licensed This is the difference between using Claude like a search box and running it like a team that ships. The guy spent 10 months figuring out what actually works so you don't have to Bookmark this

Yarchi

818,112 просмотров • 3 месяцев назад