Day 19: Phase 1 Concluded

I am very pleased to say that I have concluded the first phase of my studies.The entire purpose of this study period is to level up my skills as an Engineer and I can honestly say I feel I have succeeded.I feel my stronger in my ability to use Sublime Text 3, git, and Zsh. Throughout this phase, I also published two Node.js projects that use the Twitter API to Github that I’m very proud of. The entire purpose of this study period is to level up my skills as an Engineer and I can honestly say I feel I have succeeded.

I have added many valuable tools to my belt in this short period of time. I am more efficient as an Engineer because of Sublime’s speed, the availability of snippets, and the ability to create snippets. In git, I have learned to explicitly create branches in locations other than the currently checked out branch, which is useful for thinking ahead on projects. Adding to my Z shell scripting skill has given me the ability to be more self reliant, I can now setup MEAN stack web servers without having to wait for one of my colleagues from ops to spin one up. Undoubtably, my skills have become more valuable over phase 1.

The primary objective of Phase 2 will be to further hone my Front End Development skills. These next few weeks will include studies in html5, CSS3, and Javascript(ES5). Let’s get it!


Total Study Time Day 0-19: 159 Hours.

Day 15: Gitter


I’ve spent the last 8 days becoming more thoroughly acquainted with git, so I took it upon myself to dig deep into the .git directory and its contents. After looking around and doing some googling, I decided it would be pretty cool to build something that would be triggered by a git hook. After tweaking Tweetly, my command line tool to send tweets, it struck me that it would be cool to tweet a link to the repo of whichever project I am working on with the commit message. Git has really blown me away with it’s potential for making project collaboration, not only more contained, more seamlessly efficient.

The appeal of Github is social coding. Not only is Github a place to share our code, but its a place to share how we code. I believe the importance of this has been reinforced by various tech giants making some of their largest projects open source. The topic of making project team workflow more friendly is a topic that comes up. In the book Eloquent Ruby, Russ Olsen says “Good Ruby code should speak for itself, and most of the time you should let it do its own talking.” While that isn’t necessarily exclusive to Ruby, I believe it empowers each engineer and team when we communicate conscientiously. The quality of collaboration becomes more important as a project grows and teams (or communities) that collaborate well succeed.

I wanted to create a tool that would take the messages from commits and share them to another social platform. Gitter is a executable JavaScript file created to allow users to tweet their commit messages while they work with ease. I believe Gitter gives teams an opportunity to be more transparent and maybe even help unemployed talent land get recognition!

Until next time!


Day 8: Git A Life!


The focus of this weeks studies will be Git! Git is by far the most popular Software Version Control System to date, created by Linus Torvalds.  I have been a casual git user for approximately 4 years, when I was introduced to it by The Ruby On Rails Tutorial by Michael Hartl. It wasn’t until now that I have taken it upon myself to properly learn Git conventions and really the Git way of contributing to projects.

For learning Git and it’s intricacies, I’ll be reading The Pragmatic Guide to Git and completing a Git/Github course on Udemy.

Thus far, I am familiar with creating repositories, adding contents to a repo, and committing changes. My understanding of navigating branches and merging is just enough to be dangerous. I look forward to master about Git workflow and contributing to projects on GitHub.