It's not about the incapacity of finalizing a piece of software or choosing a new toolset.
It's not about the syndrome of the programmer willing to take up the role of the architect - those guys sooner or later will change their attitude, because the more dynamically evolving a project is, the more difficult is to manage its structure and processes.
And it's not about the architect having fun with trying out various scripting languages, he/she always has to take in account the price level of the human and technical resources, even if sometimes it hurts.
The persons demonstrating this particular weakness can be quite successful in business, and great family people or friends, but they do have at least one project, which somehow always gets reshaped and never good to go.
The problem is that those projects at some point in time have addressed a real need (or they are still addressing it), but the project owner is not feeling ready to share his/her ideas, wishes and uncertainties related to his/her solution.
Nowadays a big number of living development tools are contiguously gaining new features, we can read each day about the new versions and extensions related to the tools we are currently using or planning to adopt. It's understandable that the more professional their marketing are, the bigger the temptation is to invest time in tinkering with the latest early beta of this or that product instead of developing our own.
Put differently, we need to find day by day a good balance between making our own dreams come true, and supporting others in doing the same.
