The Fruitless Developer

We life & work in a world of "build fast and break things." Which is great. Sometimes we just need to get something built in order to fix and build off of it. The trouble is, we can end up feeling like we're spinning our wheels in a constant state of revising, never really completing a project. We never put the cherry on top, dust our hands off, and stand back admiring our architecture. That can leave us feeling, well, fruitless.

Ewan Valentine explains a similar feeling here in his blog post, How to *never* complete anything. (Talk about relatable.) 

After you read that post you'll feel a little pathetic, yet resolute. Then, head over to read Neil Green's response to the original post. His level-headed reply to Valentine is encouraging to those of us whose hearts have been in a similar place. You'll feel a lot better. You're (humbly) welcome.