Transparency. It’s an issue. Or at least, I’ve made it an issue enough to write on it. And it’s not just transparency, but the record-keeping that is associated with staying transparent.

And while writing and rewriting this post, I realized that I had once again fooled myself into thinking that talking about myself was actually useful.

It’s simple really: One extreme is to be as painfully as open as possible. The other is to shut up, and bottle it all up within. Does this really need another blog post?

It’s taken me a while to have this level of understanding of myself, and I’m sure I’ll keep learning as I go along. But seriously, these kinds of posts need to end.

Quick, To The Point!

Be open and honest, but don’t place importance on achieving openness for the sake of it, all the while sacrificing valuable time and effort. That should be reserved for creating something awesome instead.

Applications On Projects

I stand firmly on the view that ideas are almost worthless compared to implementation (this is a statement that’s a broad generalization… definitely much more to be said on this topic). But ideas are so easy to come by, and talking and writing is really easy. Or at least, I tend to talk and write about them at an elementary level, and so it may just seem easy.

This is also where transparency becomes a roadblock. To stay transparent, I try to write and talk about my ideas. From there, I just keep throwing new ideas, mixing and matching feature sets across projects.

Staying transparent has become a project all on its own. An idea without implementation.

And this must end.

Where Am I?

I don’t know how I got here. I think it’s about time I got fed up with my own lack of focus.

Here we go yet again.