Tim Yevgrashyn retweeted
AI agents are getting pretty good at writing code. That doesn't mean they need the keys to the entire network.
We've joined Agent Baseline, with @docker, @keycardai, @snyksec, @socketsecurity , @Tessl_io and @tracebit_com on the Secure Software Factory
buff.ly/xRQLAHR
THIS IS A ACTUAL F*CKING GOLDMINE
Anthropic just shared one of the best tricks for Claude Code
The idea: run Sonnet, Haiku 5.5 and Opus 5.5 at once, each doing only what it's best at
Better results and way fewer tokens: every task lands on the right model
You just start Claude Code like this:
CLAUDE_CODE_SUBAGENT_MODEL=haiku claude --model sonnet
here's how it splits:
→ Sonnet 5.5 runs the main session, writes the code, and applies fixes
→ Haiku 5.5 swarms the repo in parallel: search, grep, docs, and test audits at 340 tok/s
→ Opus 5.5 stays on call as architect for the big decisions and signs off on diffs
→ you stop burning Opus context on routine tasks and stop flooding main session with raw logs
Opus only steps in at three moments:
→ before a plan locks
→ when the same error hits twice
→ before calling it done (signing off on git diff)
Sonnet builds, Haiku swarms, Opus reviews
JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split
the full tree
> Sonnet 5.5 runs the main session and coordinates code implementation
> search maps the repo on Haiku 5.5 (read-only, 340 tok/s)
> grep finds call sites on Haiku 5.5 (0.05x cost, isolated context)
> audit scans diffs in a temporary worktree (isolation: worktree)
> Opus 5.5 on call as architect, reviews synthesized diff before sign-off
> JEV routes micro-forks in milliseconds
paste the tree and this prompt into Claude Code ↓
"Reconfigure my Claude Code setup around this tree:
1. Run the main session on Sonnet 5.5 with Opus 5.5 as architect
2. Create three custom Haiku 5.5 subagents in .claude/agents/: search (maps repo), grep (finds call sites), and audit (runs isolated diff checks in a worktree)
3. Set isolation: worktree on audit so modifications never touch my working branch
4. Add one rule to CLAUDE.md: delegate all repository searches and test runs to Haiku 5.5 subagents to keep main context under 10k tokens
5. Route fast deterministic forks (tool choice, path selection, retries) through JEV
Show me every change as a diff first. No edits until I say go"
↳ code.claude.com/docs/en/sub-…
save it, it'll come in handy
Remember, sharing is caring! You can join the Play4Agile community by clicking on the pre-registration link below.
This Post is from an account that no longer exists. Learn more
132
Medical and other humanitarian aid for Ukrainians gofund.me/bc3cd52f Direct campaign from IT-recruiting CEOs becoming dedicated volunteers. #StandWithUkraine
Project Management Institute called for sanctions against Russia and Belarus chng.it/49zFtSQ9 via @Change
Thanks to all people who asked me how to #StandWithUkriane, my native country. Here is a detailed list of what you could do to help.
github.com/AndrewStetsenko/S…
Tim Yevgrashyn retweeted
We have some news!
You can now integrate Doodle with Microsoft Teams
Read more about it here 👇👇
https://xitter.cf/t.co/hRVmB8TkA7
Tim Yevgrashyn retweeted
Homemade cloth face masks likely need a minimum of two layers, and preferably three, to prevent the dispersal of viral droplets from the nose and mouth, a video case study indicates. cnn.it/32R8OQY
Tim Yevgrashyn retweeted
Cool game creation session today with @tgoeckeler Andrea and Ilja. Thank you @yevgrashyn and @anttiki for hosting it! We develop it further
For all my friends from Play4Agile, whom I already miss - here is a friendly promo "p4aten" on ScrumCardGame.com for the next month #p4a20 #p4aten #scg #scrumcardgame
#p4a18 I'm coming there with my #playpplication
Dead or alive :-)
@Play4Agile
3
Tim Yevgrashyn retweeted
We had great session with #scrumcardgame by @yevgrashyn on Friday with students facilitated by @hsjanny Great way to enable experience.
Tim Yevgrashyn retweeted
Registration for Play4Agile North America 2017 is now open! Friday workshop will be led by @thiagi. play4agilenorthamerica.com/ #p4ana17 Pls RT
Tim Yevgrashyn retweeted
The three rules of scaling agile:
1) Descale the problem first
2) Start from the simplest solution
3) Continuously learn, improve, & adapt
















