Yes, I definitely suffer from this syndrome with my side projects. It's a great rush having an idea and the knowledge and skills to fulfill it and I think that

Yes, I definitely suffer from this syndrome with my side projects. It's a great rush having an idea and the knowledge and skills to fulfill it and I think that drives me in the beginning. When the code base is still small and uncomplicated it's fun, easy and fast to make changes, advance, add features and get instant gratification. Over time the reality of the amount of work required kicks in as well as some engineering ego. It's not enough anymore to just get something up and running...it has to be done according to the latest best practices, probably utilizing some new fangled technology I wanted to play with and it needs to be elegant, beautiful and perfect in every way. The project starts becoming less about accomplishing the original purpose and transforms more into an embodiment of my own engineering ego. Once it shows some early promise, incorporates the latest stack I wanted to play with and either hits a few major design/architecture snags that bog me down or the busy becomes too much...I loose interest. I hate it and I hate myself for working this way. I am so sick of not finishing what I start and it's the same cycle every time. Interestingly at work, it's a completely different story. It's all about efficiency, getting the thing done, tested and deployed to production because there are another million things to get done. Super focused, conscious about what is considered good enough and very little patience for other engineers who feel like they need to constantly fiddle with something instead of moving onto bigger more important things.