I can count the number of software projects I've finished on zero hands, unless you define "project" as a meaninglessly-small component of something larger (e.g. tweaking some copy). Even for software that you write to solve your own problems, your requirements tend to change over time so even that seems to never be done. With personal projects its worse, as (at least for me) they're not a way to make money so I have almost no incentive to add that last bit of polish and call it a day.
To combat this, I like to occasionally do projects with a more concrete finish - almost certainly NOT something software-related. Even something as mundane as cleaning my bedroom or some trivial home improvement type task. The more visual the result, the better.
It's so easy to get lost in this ongoing big picture that you feel like you're never accomplishing anything. I'm sure by breaking it down into smaller projects some people will better recognize their progress, but I find that doesn't work consistently enough. Maybe I'm not breaking stuff down far enough - definitely less than a day, probably a couple-hour task.
"Indeed, there is even a saying among painters: "A painting is never finished, you just stop working on it." This idea will be familiar to anyone who has worked on software."
