A Brief Introduction

There have been many times as a developer and designer that I have considered writing my thoughts, experiences and technical discoveries down, and publishing them to a blog; only to convince myself not to do it. I would fall back to a series of pessimistic thoughts and reasoning that eventually would sabotage any motivation I had. There has been a sea change, as-of-late, in my thought process on the topic, and I have to credit my experience contributing to open-source for this newly-found confidence and belief that it is worth publishing a blog on these topics.

Like many other developers who have considered similar endeavors, the thoughts that always seemed to deter me were that I would have nothing new to add to the conversation; that I would not be technically skilled enough to write on topics that could help anyone or that I wouldn’t be able to keep up with a diligent posting schedule to make it worthwhile. Outside of the last item, I believe that much of this pessimism has more to do with what is commonly referred to as “Imposter Syndrome” than actual fact. The final concern of posting regularly is more a matter of schedule, planning, and follow-through than anything else.

The transformation in this line of thinking changed as I have been beginning to work more on open-source software lately. I have had an affinity for learning new programming languages for some time now and recently have found myself really enjoying Go (Golang). Being that my primary focus as a developer is on web development, I naturally came across Mark Bates’ Buffalo project. I will go further in-depth on my experiences with it in future posts, but for the purpose of this post, I will just say that it has been very enjoyable to use. With some kind, encouraging words from Mark, I decided I would begin working on some code to contribute to the project.

I found that the same line of thinking and doubts that I had always run into while considering writing a blog, also arose when I considered contributing to Buffalo. This time though, I had the benefit of a few quick, optimistic and motivational conversations with the creator and primary maintainer of the open-source project, and that made all the difference.

I had the revelation that all levels of development add value to an open-source project; that just because you don’t feel like you are the definitive source on a set of technical problems does not mean that you cannot grow your skills by learning the problem space and contributing in a valuable and meaningful way. Most of all, I realized that we are a community and that there are plenty of other people that feel the same way you do and are willing to help contribute to your success.

I took these beliefs and began helping by developing a deployment plugin for Buffalo to my hosting solution of choice DigitalOcean. The experience was challenging at times- and is not yet fully complete- but overall has been rewarding and eye-opening. Working on Buffalo-Ocean has encouraged me to not only ignore most of the paralyzing thoughts that I attribute to “Imposter Syndrome”, but also has given me the momentum I needed to begin this blog.

My intention, schedule willing, is to post a minimum of once per week and write about a series of different topics within the arena of technology, development, and design. I will also address any technical problems, I find solutions for, that I feel may benefit others. Foremost on my agenda will be showcasing Buffalo-Ocean, and how it can be used to ease the process of deploying a Buffalo application to a DigitalOcean droplet.

I look forward to sharing with all of you and invite all corrective criticisms to posts and code that is shared on this blog. Until next time!


comments powered by Disqus