Why I'm Publishing Mediocre Content

For any reader of my blog, you may have noticed that my content isn't fantastic. In my opinion, it's mediocre at best. As I go through my life, I get ideas on what to blog about. Sometimes those ideas are easy to formulate into posts and sometimes they're not. Sometimes I have a lot to say and sometimes I don't. Regardless of how passionate I am about the topic I'm choosing to blog about, there's one thing that keeps my posts in check and limits the time I get to spend on them: time.

As a full-time software engineer, part time Master's degree candidate, full-time husband and father, and active member of The Church of Jesus Christ of Latter-day Saints, I have a lot going on in my life. I simply don't have the time to dedicate to blogging that I hope to have in the future. Believe me, I want to make these posts perfect, I want to spend time researching, drafting, revising, and polishing each post, but I simply don't have the time at this stage in my life.

So, why blog at all? Why not journal instead? Why even bother publishing if the articles aren't quite what I want them to be? I really just want a place to put my thoughts. This blog is just for me right now. A place to share a few thoughts I have with the world. I do journal, but I don't write about the details of work. This blog is a place for me to think and reason about work and the things I encounter there.

But why publish? Simple. Just like with software, if you never ship, you never get value from it. The software means nothing. Same with these posts. If I didn't publish, they'd die. They'd be forgotten and I would abandon blogging (again). By publishing, I feel like I have an audience. I feel like there's someone there that I need to be sharing these ideas with. While I know that's very false right now (my blog has extremely low traffic), I keep publishing to keep myself engaged and so the blog has meaning and value at least to me.

So, if you're reading my blog and noticing typo's or the thoughts aren't quite clear, just keep this in mind. One day I'll go back and either re-blog about the things I'm blogging about now, or rewrite the articles and update them so they're better than mediocre. For now, I'm going go at least keep writing and publishing when I have something to say.

Comments

Post a Comment

Popular posts from this blog

A Common Technical Lead Pitfall

"That item is nearly done. I just need to run it past the team lead to make sure it's good to go." Have you ever heard a phrase like that? What about something like this? "So, I had that finished and then I ran it by the team lead and he made some great suggestions to make this more reusable. Unfortunately I'll basically have to rewrite the entire thing, but it should make it easier in the future." Do you see anything wrong with either of these scenarios? What about this one? "The team lead is out of town, so that item will have to wait until she gets back so she can look it over." Situations like these come up every so often in development. There are some simple solutions to each of these. With the last one, the team lead should have designated someone to act in her stead while she was out. In the second one, the poor junior developer should have worked closer with the team lead from the start. The first one, though, isn't really an
Keep reading

Maze Generation in JavaScript

Image
This article will outline the algorithm for random maze generation with backtracking and show code examples of the steps of the process. This algorithm is obviously useful for random maze generation, but the concepts can also be applied to other areas where random input or path generation is needed. The basics of this algorithm are as follows Initialize an object to track nodes that are visited Generate the nodes in the maze. Generally you'll want to track the node's edges. You may also want to give the node an ID of some sort. If you want to cut down on recursive calls, you'll also want to track its possible edges (aka all its neighbors). You'll also want to store this as an object instead of an array as it speeds up lookup times. Choose a starting point in the maze Mark the node as visited while there are potential neighbors to visit Randomly select a possible edge to visit Add that node to the edges for the current node Add the current node as an edge on the selected
Keep reading

Leadership Experiment Update 2

This week was a bit of a slower week. A number of people that usually participate in the channel were out of town. Even still, we had some decent thoughts on these two articles: Every Day We Must Sweep and  From Engineer to Manager: keeping your technical skills . I'd like to share one observation I made: Be Vulnerable Often times as leaders we think we need to appear invincible. For some reason we think in order to lead, we can't show weaknesses. While that may be a good mindset to have towards an opposing force in war, it doesn't work well towards those you lead. If you want those you lead to follow you, you need to be vulnerable at times. You need to show them your weaknesses and how you overcame them or how you're overcoming them. This doesn't mean you need to be publicizing your weaknesses, but it could mean recognizing them when they come up naturally or sharing stories about them while mentoring and coaching those you lead. Why Be Vulnerable?
Keep reading