|
|
|
|
|
by retox
1879 days ago
|
|
If you're working on a personal project, which as others have said should give you some drive to get started, don't fall into the trap of making things too complicated too quickly. You'll get side tracked, fail to complete the core behavior and get discouraged at your own lack of progress. Set a small goal and only when it's finished start working on something else, make a kanban board with small tasks. Don't think too far ahead with "oh, I'd like to add x in the future, so I should architect y so that's possible". Don't endlessly review and refine the code you've already written trying to achieve perfection. By all means capture these next features in a notebook, but act like you're working on a 'real' project and have an actual deadline. It might also help to make commitments to show other people what you've done, I always work best when I have an audience otherwise I quickly fall into the trap of trying to make the perfect system because I know there's no hard-limit on my time. YMMV obviously. |
|