Writing Through Failure

I've been wanting to share my thoughts on Tech Leadership, Systems Thinking and Software Practices for a while. These are all topics that I care about, and where I've been lucky to have first-hand experience in companies of different sizes and maturities. There's many reasons I want to do this:

- Writing helps me reflect and put my thoughts in order.

- Sharing helps me get different opinions.

- Having a hard-copy helps me revisit topics, especially when helping others that want to learn on the subject.

But there's many reasons I ultimately don't: My career is dotted with so much failure, that I ultimately feel it's not worth sharing. I get a feeling this type of blogging is part of the content economy that reduces everything to sales. I feel my thoughts are not ready enough to share, and cast them back to the wip folder.

I found this poem[1] and post[2] by jes[3], and I found it very relatable.

blogs demand that you edit, perfect, trim, idealize anything you're about to publish. the barrier-to-entry _feels_ high.

wikis are forgiving - they don't care if you have a page called "fjlorb" that you jot random interesting words down in. wikis are life companions - they contain lists, images, projects, dreams.

I think this is a better format for what I want to write: Thoughts that are incomplete, evolving, open to grow. It's also a better way to combine my different pages. I've always been a fan of WikiWikiWeb[4], and would love something like it. I'll give the software some thought.

I don't think I'd replace my homepage with a wiki, but it would certainly change. I'm pretty excited about this idea and the prospect of actually publishing more and not getting blocked because of failure. Writing through failure is exactly what I want to be doing, it's what makes it fun and interesting.