Understanding the importance of Planning and Implementation
Lately, I’ve had a big shift in how I approach coding projects — and it all comes down to truly respecting Planning & Implementation (P&I). Before, I treated planning as something “nice to have.” Now I see it as the backbone of everything: - Cleaner architecture - Faster development - Fewer rewrites - Easier debugging - Better documentation Instead of jumping straight into code, I now focus on: ✅ Defining features and scope ✅ Breaking work into modules/components ✅ Creating step-by-step implementation plans ✅ Deciding data models, permissions, and edge cases early My Current Workflow I’m currently experimenting with: - Claude → Planning, architecture, and system design - Gemini → Writing the actual code - Claude again → Reviewing the implementation This has massively improved consistency and reduced rework. At the same time, I’m intentionally trying to keep Claude token usage low on my Pro plan Any ideas on how to automate this process?