Hey everyone! I'm currently working on a personal project and I feel really excited about it. I have a great idea and a good grasp of what it'll take to build it. However, I've never transitioned an idea through design to implementation before. At my previous job, I got some exposure to design documentation and architecture models, but I wasn't the one creating them—they were mostly for new features in existing products.
Now, I feel somewhat overwhelmed and unsure about when to stop designing. How do I determine if I've done too much design or too little? When is it time to dive into coding? And are there any recommended resources like books or websites that could help? I'm eager to get started but want to avoid the trap of over-designing. Thanks for your help!
3 Answers
Look into terms like 'structured programming' and 'minimum viable product.' The amount of design you do should match what you can realistically deliver in a specific timeframe. Consider rolling out features progressively and always keep documentation in mind—it’ll save you!
It really depends on the individual. I struggle to finish projects when I overthink them. I find it best to start with minimal functional code and iterate from there. Focusing on writing loosely coupled, testable code helps, especially if you're using architecture principles from your past experiences.
In corporate environments, many think the waterfall method is resource-efficient. But in reality, it often isn't. You might prefer the iterative method, where you build what you think you need, assess what works and doesn't, and adjust accordingly. Just be prepared to potentially rewrite parts of your code as needed.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically