An Open Way to Do Something

Long time without a post. But this time I have a reason. And not only that, but the reason that I bring to you this time is quite powerful. I’ve applied bad execution practices.

Guess what. I have a couple of half-done posts that are waiting to “get finished” to be published. The problem is I haven’t had the time to polish them till the point I’m comfortable enough to consider them final. But the truth is that there ain’t no such thing as a free lunch, or a final release. Everything is a work-in-progress, until some day when we stop working on it and becomes an abandoned work-in-progress. If we share our projects with the world maybe they will be useful for someone; but usually we have our egos mediating the road to project starvation before someone ever gets to know we’ve been working on something.

And this is just a blog right? A dead post is no big deal. But the pattern tends to go on to larger endeavours. Software projects, research projects, books, music, films, and a lot more. But then someone came up with a great idea:

Why not make the whole process open?

And open source was born. To open source something (and not only software) means that you accept to make public your mistakes, as well as your successes. To benefit others and be benefited. To criticize and be criticized. To teach and learn.

A gift that came with the Web 2.0 and further with activity streams (like Twitter or –less– Facebook) is the capability to trust other people. That one is also a gift of the open source community. The world is not a zero-sum game and collaboration is our most powerful key to success.

So I propose to you:

Don’t wait to get your project finished, if you can articulate your vision you’re good to go.
Share your visions with the world an let’s build’em together.