Make sure you have not only an idea, but an idea of how to execute those ideas. I believe you should focus on one of them although this is based on my preferenc

Make sure you have not only an idea, but an idea of how to execute those ideas. I believe you should focus on one of them although this is based on my preference for sequential-like implementation [0]. If you're still pressing ahead of parallel; 1) keep excellent documentation that even a hired programmer can follow. 2) ensure you don't forget to eat, drink, exercise, etc. Fixed habits help tremendously. 3) have a plan to cope with information overload. eg, HN is full of links that help your project and your project ideas. My plan is that unless the links are very very good, you're already implementing it. You could bookmark it as "Research later" (tip: ensure the bookmarks are descriptive. eg Nginx security guide [1]) 4) Adopt a 'write down and forget', eg logbook. A calendar is great for events. There's more tips but I need to get back on my project. [0] I've attempted parallel implementation, the burnout and confusion comes much faster for me despite all my tips above. [1] https://calomel.org/nginx.html https://calomel.org/nginx.html