Haven Vu @havenvu - Twitter Profile

Pinned Tweet

about 1 month ago

I’m a top 1% codex and claude code power user. 8-10 terminal tabs always running simultaneously. Hit $200 weekly limit in 1 day. Here are some of my biggest tips. Seriously plug this into your codex or Claude code and ask how you can begin doing this. 1. Stop caring so much about managing context windows. It’s always better to have large agents.md or Claude.md files and burn tokens than have your agent forget details and implement incorrectly. You’ll end up burning way more tokens and wasting way more time if you try to token optimize. Models typically get better and their context windows go up over time anyway. Don’t worry so much about having the perfect context length. That is very short sighted. Instead, you should have a memory log, decision log and a large instruction file so that literally every session has full context on what you’re trying to accomplish. 2. To make faster decisions, tell your agent to ask YOU questions on what you believe the ideal user experience is and work backwards. This will help you understand the tradeoffs of complex architecture without having to understand all of the nuances in architectural decisions. It’s always better to work backward from the user experience because you’ll likely end up refactoring any architecture to cater to a user experience anyway. I’ve refactored my architecture so many times because of some UX issue as opposed to some security issue/ logic issue. 3. To work in parallel, spawn multiple work trees & use docker. However, shipping and integrating with main should always be done sequentially. Shipping and integrating into main will take likely the same amount of time as building all the features out in parallel. But if you try to parallelize many agents writing to main in parallel your code will break. 4. Build harnesses and headless testing for EVERYTHING. The faster your AGENT is able to test its work, the faster you can ship, so spend time building tools for your agent to close its own loops. Without you needing to verify manually. 5. Start barebones with vanilla agents — I’ve uninstalled almost all MCP connections. Almost all of my skills and tools were just coming from workflows I found myself using repeatedly out of vanilla use. Just give your agent knowledge that certain tools exist and they can call it on demand. Otherwise just build your own skills. 6. To prevent your agent from lying about being “done” with a task: Always pair program with another model. The way you do that is to give your agent access to Claude code CLI and Codex CLI and Cursor CLI and Devin CLI as tools/ skills. These CLIs have the best unit economics for calling coding agents. You may end up burning 2x the tokens but you’ll save a ton of time and that will let you ship so much faster (for me 5x faster) because I’m able to have my agents run longer loops when it works with a pair programming agent. While it burns tokens, I can go ship another feature or work on something else. 7. Build your own tutor and spin up small internal tools and web apps to help you read through your codebase simply. Use excalidraw for diagrams and just have your agent teach you the codebase and update its own documentation as the codebase grows. When I was building out my mascots I literally had my agent build out a webpage for me to see all 150 iterations of my mascot. Why would I click through a complex file system when I can literally one shot internal tools for myself? Make yourself work more efficiently with the agent.

0

3

0

263

Haven Vu

@havenvu

Last Seen Users on Sotwe

Trends for you

Most Popular Users