Dead Code πŸ’€ (@imdeadcode) header
Dead Code πŸ’€ (@imdeadcode) profile picture

Bury the past, code the future!

San Francisco
Joined February 2018
Replying to @poteto
@poteto's AIE talk in one line: code review is shrinking into proof review. Her tokens are going to 70% verification vs. 30% implementation. Key ideas: - Give the agent the ability to run the code for itself - A feature map: a sitemap for your App - Property-based UI tests
1
31
Ever see someone on X and wonder how they actually make money? I got tired of digging by hand, so I built a free Claude Code skill. Give it a profile or post. It pieces together the likely business model, labels what holds up, and gives you a blueprint.
3
1
58
Just read @AnthropicAI post on writing effective tools for LLM agents and it completely changed how I think about testing AI tools🧡:
1
17
Building Block #7: Feedback - Human oversight workflows. Some decisions are too important for full automation - like customer emails or purchases. Add approval steps where humans review before execution.
1
6
Building Block #6: Recovery - Graceful failure management. APIs go down, LLMs return nonsense, rate limits hit. You need try/catch, retry logic with backoff, and fallback responses. Standard error handling 101.
1
4
Building Block #5: Control - Deterministic decision-making. Don't let the LLM make every decision. Use if/else, switch cases, and routing logic. This is normal business logic - the same you'd write in any application.
1
5
Building Block #4: Validation - Quality assurance for LLM outputs. LLMs are probabilistic and inconsistent. Validate JSON against schemas, retry on failures. This ensures your downstream code can reliably work with the data.
1
4
Building Block #3: Tools - External system integration. Pure text generation is limited. You want to call APIs, update databases, and read files. The LLM says, "call this function with these parameters" - your code handles execution.
1
5
Building Block #2: Memory- Context persistence across interactions. LLMs are stateless; they forget everything after each call. You need to manually store and pass the conversation history. This is just normal web app state management.
1
3