this is pure f*cking treasure
A Stanford AI research group has found a way to use JEV to make your LLM run 24/7 at a lower cost in x444
the LLM only does what needs words. everything else is a typed decision:
> worth reading? Jev answers yes or no before a single token is spent
> which desk? papers, repos or market, one Choice
> rerank: embeddings pull 20 sources, Jev keeps the 5 that matter
> claim holds? every claim checked against its source, the weak ones dropped
> new or known? duplicate, related, revises or contradicts, checked against the vault
the LLM writes one note, 5 to 12 lines, one claim
> judge: confident verdicts pass, unsure ones go up to a frontier model
> matters to you? only the top scores make the morning brief
the judge rule comes straight from Carnegie Mellon's JEV-as-a-Judge paper: escalate only the unsure 34%, keep 99.6% of the accuracy at 47% of the fee
and the fees are the whole point
> Jev: $0.044 per 1,000 judgments
> GPT-6: $12.182 for the same 1,000
a whole day of decisions on a frontier model costs dollars. the same day on Jev costs cents
you stop reading 300 sources. you read one brief
Full Claude Course
Master Claude to automate repetitive tasks, build apps without coding, create real portfolio projects, and become more valuable at work.
this is pure f*cking treasure
how to build your first ai agent (full walkthrough)
if this had landed in front of me a year ago, my first agent would've shipped in an afternoon instead of eating two weeks of my life
in the right hands it resets what one person can ship alone:
Starting September 14, we're permanently raising standard weekly limits in Claude Code by 25% for Pro, Max, Team, and seat-based Enterprise plans. Until then, the current 50% increase will be in place.
If you're serious about DevOps, these 7 repos will teach you more than any course:
1) The Book Of Secret Knowledge:
↳ https://t.co/u9v3ONDMj6
2) Awesome Scalability:
↳ https://t.co/wv88mkpjQH
3) Awesome Cloud Native Trainings:
↳ https://t.co/DfLm7quPaw
4) DevOps Exercises:
↳ https://t.co/ulbnupaeUM
5) How They SRE:
↳ https://t.co/vrikybZR5d
6) Test Your Sysadmin Skills:
↳ https://t.co/FQJpfTE2aT
7) How They DevOps:
↳ https://t.co/XO70w3krvQ
CLAUDE + OBSIDIAN + LOOP ENGINEERING = AN AGENT THAT LIVES IN YOUR NOTES
Karpathy's second brain runs on something close to this. two years of growth. he barely typed any of it
four steps, on repeat:
1. read - Claude Opus 5 opens the vault, not a chat window
2. write - notes and links change inside a branch
3. check - a critic reads the diff, checks every link
4. keep - the good change sticks. nothing gets touched
cost: 2-4x a single prompt. worth it past a 5% gain. zero notes overwritten. the vault only grows
the whole system runs on six plain files: CLAUDE.md, skills, subagents, hooks, MCP, plugins. no black box
three ways in: a desktop connector for three clicks, Claude Code for full control, or the Obsidian plugin if you never want to leave the app
append, don't overwrite. measure the win before adding a step. never let it rewrite the whole vault in one turn
a loop that never deletes a note is compound interest for your own thinking
GOODBYE EXCEL.
🚨Claude designs a full FINANCE DASHBOARD like a $9,000 analyst. For free.
Here are 8 prompts to build yours.
Save these prompts. Build your dashboard later. 🔖
🚨 NO CLIENTS? 6 MONTHS BUILDING, STILL $0 REVENUE.
THE PROBLEM WAS NEVER THE PRODUCT — IT WAS SALES.
DROP YOUR LINK: THIS AI FINDS YOUR BUYERS, WRITES THE EMAILS, BOOKS THE CALLS.
$30 FREE CREDITS, ONLY 9 LEFT — GONE TONIGHT 👇
https://t.co/zIoFBagUPx
ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT
you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back.
question → scope → 5 searchers → dedupe → writer → fact-check → report
the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles.
5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source.
dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant.
the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it.
the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten.
nothing reaches you until a second agent, with clean context, has tried to kill it.
12 minutes, 40 sources, one report where every line traces back to something real.
save this and read the full graph engineering course below ↓
A senior Anthropic engineer just dropped 12-page PDF on "Graph Engineering" for multi-agentic systems.
The shift: your agents memory dies with their context window. A knowledge graph makes it permanent.
Extract → Resolve → Assemble → Query → Repeat
Every agentic graph has 5 stages:
• Extract: Haiku pulls entities and S-P-O triples. One call per doc. The Pydantic schema is the only training data.
• Resolve: Sonnet clusters "Edwin Aldrin" → "Buzz Aldrin" - zero string overlap - using descriptions as context.
• Assemble: canonical nodes, typed edges, provenance on every triple. One connected graph.
• Query: serialize a subgraph → Sonnet reasons over triples → every answer cites a specific edge.
Plug this into multi-agent systems as shared memory.
Workers write to it, evaluators fact-check against it, loops persist overnight with it.
This 12-page PDF changed how I'm building multi-agent systems today.
Read it now, then explore the article below.
My friend applied to 250 tech jobs in two years. No MIT. No Stanford.
Last month Anthropic offered him $750,000.
I asked him how he broke in from zero.
He sent me the exact video that got him in. Anthropic's 2-hour course on how to become an AI engineer in 2026.
Thariq Shihipar shows you exactly how to build AI agents from scratch.
I watched it last night.
Halfway through, I realized I could break into an AI lab in months, not years.
Bookmark this and read the article below.
• 00:00 - AI agent harness
• 23:44 - building AI agent loops
• 56:39 - AI agent context engineering
• 1:33:34 - AI agent deterministic hooks
• 1:50:31 - Anthropic SWE interview process
I was laid off by Amazon AGI today, along with many of my colleagues.
My job was deciding which data points matter for pretraining. Turns out I was the one that got filtered out.
At 1pm, the reminder for our weekly project sync still went off — for a project that no longer has a team. We could only exchange a smile that needed no words.
More seriously: everything I've worked on has been about data, data curation pipeline, data reordering, and data uncertainty. I’m actively looking for new opportunities, including pretraining, trustworthy LLMs, safety, and LLM efficiency — please reach out if you have any openings!
To my manager and teammates: thank you for all the help and support you've given me along the way — I learned so much, and I loved the work we did together. It was a great journey, and I know even better ones are ahead for each of you.