Girish (@SharmaGee_) header
Girish (@SharmaGee_) profile picture
Joined February 2021
Photo by Girish (@SharmaGee_)Photo by Girish (@SharmaGee_)Photo by Girish (@SharmaGee_)Photo by Girish (@SharmaGee_)Photo by Girish (@SharmaGee_)
Girish retweeted
How to Process Your Anger and Rage — Dr. Gabor Maté
15
45
3
502
60,922
I went through AI Engineer job posts this week. Almost none of them asked for another chatbot demo. They asked for proof you can make AI work in production. Here are 15 AI engineering projects that will actually get you interviews: • RAG system with hybrid search, reranking and cited answers • Eval pipeline that catches regressions before every deploy • LLM gateway that routes between models by cost and latency • Semantic cache that cuts your API bill • Fine-tuned small model that beats a big one on a narrow task • Structured output extractor with schema validation and retries • Prompt versioning system with A/B testing • Hallucination detector that flags unsupported claims • Voice agent with speech-to-text, LLM and text-to-speech under 1 second • Document pipeline that parses messy PDFs, tables and scans • Observability dashboard for tokens, cost, latency and failures • Local LLM deployed on your own GPU with an API • Agent with tool calling, memory and human approval steps • Red-teaming suite that tests your app against jailbreaks • Synthetic data generator for training and testing A demo shows you can call an API. Production shows you can be trusted with one. Pick 2. Ship them. Share the numbers. Bookmark this for your next AI job hunt.
40
69
7
663
33,686
Girish retweeted
i still can't comprehend why senior engineers run claude code on default configuration. one settings change and every model gets its own job: → opus 5.5 architects every plan and unblocks when stuck → sonnet 5.5 writes the production code → haiku scouts file paths and line numbers with zero overhead → a critic agent tears your diff apart before you merge Opus thinks. Sonnet builds. The cheap models grind. paste this into claude code Add this to ~/.claude/settings.json. Keep every hook, permission and plugin I already have. Then create the two agent files below and show me the diff. ```json { "model": "opusplan", "advisorModel": "opus", "effortLevel": "medium", "modelSettings": { "claude-opus-5-5": { "effortLevel": "high" }, "claude-sonnet-5-5": { "effortLevel": "medium" } }, "env": { "CLAUDE_CODE_SUBAGENT_MODEL": "haiku" } } ``` ~/.claude/agents/scout.md ``` --- name: scout description: finds code fast. returns file paths and line numbers only. model: haiku tools: Read, Grep, Glob --- Locate exactly what was asked. Return file:line. No fixes. No opinions. ``` ~/.claude/agents/critic.md ``` --- name: critic description: reviews a diff or plan before any task is called done model: opus tools: Read, Grep, Bash --- Assume this is broken. Find how it fails. One line per issue, worst first. ```
19
56
1
637
55,604
This is f*cking insane. Andrej Karpathy: "Vibe coding is amazing. But Agentic + Opus 5.5 harness engineering is the next level. 99% of my coding routine is automated by AI agents." In this 30-minute talk, Andrej Karpathy walks through building an AI agent workflow from zero. Worth more than any $500 agentic engineering course online. Watch it today, then read The Karpathy Playbook below ↓
37
25
3
264
56,676
This is f*cking insane. Anthropic engineer: "You're not supposed to prompt Opus 5.5 You're supposed to build a system that prompts itself. At Anthropic, 90% of our engineers have already built these systems" In 30 minutes, she walks through exactly how Anthropic builds agents that remember, fix their own mistakes and get sharper with every run. Better than any $1000-$2000 agent course I've seen. Watch it, then read the article below ↓
Readers added context they thought people might want to know
Lamis never says "You're not supposed to prompt Opus 5.5” in here talk at AI Dev Con. The caption misrepresents the video knowing most won’t watch the video all the way through and jump to the articles. youtube.com/watch?v=tTcxVv…
217
666
43
8,821
1,637,283
Weekend hack: HackerTube. I was annoyed with YouTube's recommendations so I had Claude filter down 43M comments over 20 years of HN to 6,454 videos that keep being recommended. *Significantly* better viewing experience, ~2 hours with Opus 5.5: hackertube.org/ - Excellent recs without any logins (state is kept in local browser session) - Thumbnail is a representative frame from middle of the video instead of the super duper A/B test hyper-optimized user uploads - Underlying data from the comment analysis as one zip file, point your Claude at it and ask for your own version - HackerTube Longs ✊ A bit more on the process: I use Claude Code (desktop app for Mac), Opus 5.5 on Medium effort as my default. I only talk to Claude and have it do everything, the only "manual work" I helped with in tandem was in the browser (reminiscent of MenuGen): 1) I had to create some kind of API key from Google Cloud UI to query YouTube for video metadata, 2) I booted up a VPS box for serving and 3) I bought the domain name. Once the box was up I gave Claude the IP and told it update, secure, harden, deploy and optimize the code, and it did the whole thing. Many awesome projects that would have normally taken weeks/months even can now be few-shotted for breakfast. What else are we not thinking of.
2,392
4,849
1,810
52,453
5,775,796
Karpathy 开炮了(前 OpenAI、前特斯拉 AI 负责人): "Agent 不是魔法,是大规模蒸馏。你模型 99.99% 的容量,都浪费在它根本不需要的数据上。" 16 分钟对谈,他给出了真正有效的技术栈:小模型、正确的工具、一个闭环。 大模型 → 小模型 → 正确工具 → 闭环 → 自我改进的 Agent 别再为更大的模型交税了,让小模型变危险的,是闭环。 这 16 分钟,比今年任何 500 美元的 AI 课都值。看完再读"Harness, Loops, Graphs"——闭环就是那副马具 ↓
107
175
16
1,180
123,195
Stanford CS329Z: Engineering AI Agents is so underrated on YouTube. It literally walks you through everything you need to build your own AI agent, step by step, hands-on. Skip Netflix and those endless short videos. Pick a topic that interests you and dive in this weekend. It might just help you land your next $500K job. youtube.com/watch?v=b4y3rjGp… course website: cs329z.stanford.edu/
24
275
6
2,284
116,096
A lot of content engineering challenges have pretty standard solutions, which has lead to some engineers saying agent engineering is solved/boring True to some extent, but there are a bunch of (fun) new ones emerging as agents evolve!
218
72
37
642
93,946
Girish retweeted
This is f*king insane. SpaceXAI engineer Lauren Tan: "You spend the tokens to set up a codebase so that even the dumbest agents can do a good job." In this 60-minute workshop, she shows why the setup matters before you scale the team Job → Rules → Skills → Verification → 6 Bots → 200+ Agents* Most people add another bot when the first one fails. That just multiplies the mistakes Spend the tokens on rules and checks once, instead of paying for the same failure every run Worth more than most $1,000 agent engineering courses Bookmark and watch it today Then read the full setup: "Grok Bot: 6 Bots, 200+ Agents, a Smaller Bill" ↓
Your Grok Bot is not expensive Your setup is 75% of my Grok Bot tokens went to re-reading old chat. About 1% went to actual work I broke down the 6-bot setup the Grok Bot team runs, and the 9 leaks eating your bill ↓
58
386
16
3,480
410,916
Girish retweeted
Your Grok Bot is not expensive Your setup is 75% of my Grok Bot tokens went to re-reading old chat. About 1% went to actual work I broke down the 6-bot setup the Grok Bot team runs, and the 9 leaks eating your bill ↓
155
132
43
1,216
2,057,900
Girish retweeted
This is a goldmine for anyone building with agents. Stripe just shared their internal AI agent setup. Same task: 20 days with plain Claude Code, 4 days with theirs. And you can copy it. The setup is a "factory" for work they keep repeating. Every step lives in its own saved prompt, one agent builds while a second one watches it, and after every run the prompts get better. A payment integration used to take up to 6 months. Now it takes 2-6 weeks. Here's how it works: 1. One prompt per step. They studied 125+ past integrations and turned every step into a reusable prompt. They have 100+ of them now. 2. An agent that watches the agent. While one agent builds, a second one reads its transcript and notes where it got lost, what it had to re-learn and which tools failed. Engineers use that to fix the prompt. 3. Prompts that update themselves. After every run the agents leave learning logs, decision logs and review comments. Another agent turns them into prompt fixes, and some get applied in one click. 4. Code runs the agents, not an LLM. They first used an AI orchestrator. It was slow, expensive, and sometimes did the work itself instead of delegating. So they rewrote it as plain code. 5. Agents test their own work. They run test payments in sandboxes before any human reviews the PR. To copy it: save every prompt that worked, have a second agent review the transcript, and fix the prompt instead of fixing the output.
95
43
5
542
36,807
We're redefining the SDLC for the agentic era. Lots of GitHub updates this morning at Universe: • GitHub Copilot Fusion delivers frontier-level quality, 40% faster and at up to 77% lower cost • Our unified Copilot harness is now in Foundry, a managed service for building long-running agents that reason, use tools, and get work done • Copilot Projects gives you an orchestration loop to build with multiple agents across repos And we’re expanding capacity and strengthening GitHub’s architecture to make the home of agentic development more resilient.
202
203
47
1,607
252,663
Girish retweeted
强烈推荐斯坦福的这套关于 AI Agent 的课程,对于有志成为 agent engineer 的同学可以看看:cs329z.stanford.edu/
25
346
9
2,553
158,012