Loading video...

Video Failed to Load

Go Home

What happens when you give the quant trader’s bible to two frontier AI models? The Green Book is what traders use to prepare for firms like SIG and HRT, where I interned. And in high-frequency quant trading, being right isn’t enough. You have to be first. Inside Codex, I...

25,335 views • 20 days ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 views • 2 months ago

-> If you’re looking for a job -> right now, there are three -> Claude certifications that -> you should do this week -> and then put them on your -> LinkedIn, they are all -> completely free, and they -> come from Anthropic, -> which is the company -> that's behind Claude. -> And jobs that need AI skills -> pay 56% more than jobs -> that don’t, So, I think -> spending a few hours this -> week to knock out these -> three courses and then -> add them to your LinkedIn -> will really go a long way -> The first one is called -> Claude 101, and this -> essentially just goes over -> what Claude is and when -> you should use chat versus -> co-work versus code, how -> projects and skills work, -> and how to connect all -> of your tools and apps -> like Gmail, Notion, Slack, -> and other tools that you use -> And the second course -> is called AI Fluency -> Framework and Foundations -> Inside this one, there are -> 13 lessons on how to -> actually work with AI. -> It goes over things like -> effective prompting, critical -> thinking on the outputs, -> and it has a vocabulary -> sheet that you’ll want -> to read and save for later. -> And the third one is -> Intro to Claude Cowork -> Claude Cowork is where -> you can actually get stuff -> done with Claude. -> So, this course covers -> projects, skills, plug-ins, -> scheduling tasks, handling -> files, and then also how -> to pick the right model -> for the job, and then when -> you finish these courses, -> just go to your LinkedIn -> and go to your profile -> Click "Add section," and -> then go to "Licenses -> and certifications" and -> add all three of these. -> And then when you land -> the interview, you should -> talk about your AI fluency -> often as you possibly can -> I feel pretty confident that -> you’ll truly be able to -> differentiate yourself -> from other candidates -> if you do this

BeingInvested

13,130 views • 3 months ago

I built an agent that answers machine-learning questions. It's autonomous, and the best part is that I built the whole thing without writing a single line of Python code. Here is what I did and how I did it: Over a year ago, a friend and I built a site that publishes multi-choice questions. You get a new one every day. I decided to have GPT-3.5 answer questions. Here is what I needed to build: 1. Connect to the site's API to retrieve today's question 2. Extract the question and the potential choices 3. Connect to OpenAI's API and ask GPT-3.5 to answer the question 4. Parse the answer from the model 5. Submit the answer back to the API to get the score Not difficult. Likely several hours of work. But I didn't have to write any code. I built the whole thing by dragging and dropping components using Vellum is a YC-backed platform for developers to build LLM applications. They are the only ones I've seen offering this functionality. They sponsored this post, and their team helped me with all my questions while I built this. I created a workflow. The platform supports several node types to build whatever you have in mind. I show how I put the whole thing together in the attached video. The only code I had to write was a few lines of Jinja to parse and transform the API and the LLM results. There are three lessons I want to share from this experience: First, the best possible code is the one you didn't write. I'm a big fan of no-code tools because they help me materialize my ideas fast. They help product people, designers, and no coders collaborate on the solution. Second, Large Language Models are sensitive to how you prompt them. Small changes to prompts can make a big difference in results. This is more pronounced when you are building a multi-step workflow. Third, automated testing and evaluation for prompts is critical. There aren't many companies thinking about this. They'll have a hard time moving from a demo phase. The attached video will show you what I did.

Santiago

309,825 views • 2 years ago

GPT-5.6 vs GPT-5.5 on my custom spaceship prompt. I gave both models the exact same custom prompt. This is also the same prompt I previously gave to Fable 5. For context, GPT-5.6 Pro worked for 87 minutes, while GPT-5.5 Extra High worked for 34 minutes and 42 seconds. As I’ve said before, based on great authority GPT-5.6 will be an incremental/soldi improvement over GPT-5.5, not a “Fable killer.” My rough expectation has been that it would trade blows with Fable 5 on some benchmarks, maybe win around half depending on the category, but not clearly surpass it overall. And again fable five will have bigger model smell, but this was expected. After testing this coding output, that view feels pretty accurate. GPT-5.6 is clearly better than GPT-5.5 in several visual areas. The lighting, shading, chairs, object details, and exterior of the spaceship looked noticeably stronger. The scene was also easier to test. I do want to give GPT-5.5 credit though. It built out the rooms much much better and the planets looked better than GPT-5.6’s. It was also interesting that both GPT-5.5 and GPT-5.6 produced better-looking planets than Fable 5 in this specific test. The downside with GPT-5.5 was stability. The game was much glitchier and harder to test compared to GPT-5.6. But when it comes to the core of the demo, which is the spaceship itself, Fable 5 still beat both models pretty comfortably. GPT-5.6 is impressive, but from this test, it looks exactly like what I expected which was a meaningful incremental improvement over GPT-5.5, at least for indie game demos, but not something that replaces Fable 5. In collaboration with Chetaslua

Chris

250,919 views • 2 months ago