I have sort of the same problem, Dennis.
Try starting the project well before you've solved the problems. Just start. Literally anywhere except for the algorithmic or new-skill parts.
Start in the middle. Start with the tests. Start with a command line app. Start with a UI. Whatever.
Since the enjoyment for you lies in solving the juiciest problems, do the parts of the work that are trivial FIRST and save your dessert for last.
Good suggestion. Will definitely try something like this for my next project! Maybe even on my current project that I have stalled. Try to reopen it and take this approach. Thanks :)
Go for it my friend
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have sort of the same problem, Dennis.
Try starting the project well before you've solved the problems. Just start. Literally anywhere except for the algorithmic or new-skill parts.
Start in the middle. Start with the tests. Start with a command line app. Start with a UI. Whatever.
Since the enjoyment for you lies in solving the juiciest problems, do the parts of the work that are trivial FIRST and save your dessert for last.
Good suggestion. Will definitely try something like this for my next project! Maybe even on my current project that I have stalled. Try to reopen it and take this approach. Thanks :)
Go for it my friend