Amazing article from one of the best in AI space! Using your own app is super important here - the best way to find bugs and stuff that’s not working as intended.
The context window point is the one nobody talks about enough. I've watched builds go sideways specifically because the AI lost track of what was decided 200 messages ago. Starting fresh sessions for discrete tasks felt wasteful at first - now I do it automatically.
Version control from day one is non-negotiable. I've had agents make changes across 12 files in a single session and without git, tracing which change broke what is nearly impossible.
The thin vertical slices principle is most underrated here. Ship something working end-to-end before adding breadth. Sounds obvious, somehow hard to actually do when the AI makes adding features feel cheap.
Thank you for sharing these amazing tips Jeff & Wyndo. Lazy prompts is something I’m guilty of while vibe coding. For mistake #4, I loop in notion as my knowledge base for projects via MCP, so that I can maintain persistent project context (PRDs, change logs, epics/stories, etc). So I’m able to clear chats once I feel Claude is overburdened with context. Do let me know if you have any suggestions to improve this setup.
Jeff, this: "I try to clear my context (open a fresh session) before I hit 50%." You are so disciplined!
One funny thing I found with Cursor is that, if I keep using the context window, I'll actually create a new chat session with the same name + {1}. That kind of resolves the problem.
Heck yeah! Thanks for having me on to share!
Amazing article from one of the best in AI space! Using your own app is super important here - the best way to find bugs and stuff that’s not working as intended.
Great tips here, Jeff!
Thanks a bunch Ilia!
Great read, thanks for sharing.
Thanks for the builder tips for the good 😊
I'm glad it was helpful!
I love the kind of things your talk about!
The context window point is the one nobody talks about enough. I've watched builds go sideways specifically because the AI lost track of what was decided 200 messages ago. Starting fresh sessions for discrete tasks felt wasteful at first - now I do it automatically.
Version control from day one is non-negotiable. I've had agents make changes across 12 files in a single session and without git, tracing which change broke what is nearly impossible.
The thin vertical slices principle is most underrated here. Ship something working end-to-end before adding breadth. Sounds obvious, somehow hard to actually do when the AI makes adding features feel cheap.
Thank you for sharing these amazing tips Jeff & Wyndo. Lazy prompts is something I’m guilty of while vibe coding. For mistake #4, I loop in notion as my knowledge base for projects via MCP, so that I can maintain persistent project context (PRDs, change logs, epics/stories, etc). So I’m able to clear chats once I feel Claude is overburdened with context. Do let me know if you have any suggestions to improve this setup.
Jeff, this: "I try to clear my context (open a fresh session) before I hit 50%." You are so disciplined!
One funny thing I found with Cursor is that, if I keep using the context window, I'll actually create a new chat session with the same name + {1}. That kind of resolves the problem.