AI Pair Programming Etiquette: The Unwritten Rules
Sophie Chen द्वारा
Rule 1: Understand Before Accepting
Never merge code you don't understand. The AI is your assistant, not your replacement.
Rule 2: The 80/20 Split
Let AI handle 80% of boilerplate. Spend your energy on the 20% that matters: architecture, edge cases, security.
Rule 3: Maintain Your Skills
Code without AI for 2-3 hours weekly. Solve LeetCode problems manually. You need a foundation to review AI code.
Rule 4: Document the Why
AI writes code. You write why it exists. "// Handles race condition when user clicks twice" > no comment.
Rule 5: Review Like a Senior
Treat AI code like junior developer code:
- Check for edge cases
- Verify error handling
- Look for security holes
- Question architectural decisions
Rule 6: Take Breaks
AI makes you faster. That doesn't mean code 12 hours. Ship faster, then log off.
Rule 7: Credit Appropriately
In code reviews: "Generated initial implementation with Cursor, then modified X, Y, Z." Transparency builds trust.
Build Blueprint · Creator
कोई आइडिया है? वह स्पेक पाएँ जिससे आपका AI एजेंट बना सके।
किसी भी प्रोडक्ट का वर्णन करें और एक संपूर्ण बिल्ड ब्लूप्रिंट पाएँ — स्टैक, डेटा मॉडल, स्क्रीन, API और Claude Code या Cursor के लिए तैयार-पेस्ट प्रॉम्प्ट। PDF में एक्सपोर्ट करें।
ब्लूप्रिंट खोलें ▸