Day 24: What’s up DOC!


I have taken the past couple of days to brush up my knowledge of html and to familiarize myself with its newest features. In the advent of the web, Hypertext Markup Language, more commonly known as html, was the language used to create web pages. Since then, the web has become vastly more sophisticated, with the creation of CSS and Javascript, among other technologies. As the web has become more advanced, so has html as a markup language.

The most recent iteration of html, html5, has build upon the foundation of its predecessors with both the developers and users in mind. Prior to html5, developers were forced to use the div element very generously. Now, developers can use html elements such as header, article, section, and footer to markup their web content. Not only are these new elements helpful for teams of developers to create and keep html documents organized, but this also helps users who access web pages via accessibility devices. The html5 document declaration is also valid for XHTML.

html5 also includes updated element attributes, embedded video, and animations. Forms, in html5, can now input email, date, telephone number, and time types. All of these attributes can help search engines when they index html pages to assist the users in finding more relevant information to their query. Previously, developers would have to employ a service like Adobe Flash to embed a video into a webpage. With html5 video, Flash and other services are now optional for embedded video for now. Canvas, an html5 feature that requires Javascript, can be used to create vector images in a web application.

Both the web and html have come along way, since their creation. Hypertext markup language 5 can now be combined with CSS to create responsive web pages. The most advanced features of html5 require the use of Javascript, such as Canvas and the  Geolocation API. This is only really scratching the surface of html5 (I will cover more advanced features of html5 in a later blog post).

Not all browsers have transitioned to completely support html5. A browser that does not support it may not recognize html5 elements and the content is ignored. To address this issue, html5 shiv was created. Shiv creates  in Javascript, so that the browser can natively recognize and style. Thanks to Josh Hibbert, I have this awesome Sublime Text 3 html5 shiv snippet.

Until next time!


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!