Day 52: Sassy!


In the world of Front-End Development , use of a CSS preprocessor is of massive import. Today, there are many CSS preprocessors available for teams and engineers alike to use, such as LESS, Sass, SCSS, and Stylus. It is very common for Front-End Development frameworks, such as Bootstrap and Foundation, to be built using a CSS preprocessor. Preprocessors empower designers and programmers to optimize their CSS utilization by systemizing the process. The benefits of using a CSS preprocessor are many and they are definitely here to stay.

Preprocessors are very beneficial. While many will argue that creating CSS is not technically programming, using a CSS preprocessor gives creating stylesheets a programming feel. In almost all preprocessors selectors can be nested, extending the rules from parent selectors to their children. Reusable variables are also common in preprocessors, which allow for code to be more modular and readable. Like many programming languages, developers can utilize many built-in functions and, if they need a custom solution, create functions of their own. Once the code is processed into CSS, the resulting stylesheet is standardized and easy to read. Above all, CSS preprocessors are more programmer friendly than standard stylesheets.

In my own studies, I have decided to make SCSS my preprocessor of choice. In my opinion, SCSS has syntax more similar to vanilla Javascript, which I really like. Using SCSS has helped me be more efficient writing CSS. I really enjoy using partials, which make my code so much more organized, especially when stylesheets become really long. I also like that pure CSS is valid SCSS, so if I’m in a crunch I can find a way to solve an issue in CSS and it won’t break the rest of my code. I look forward to continue mastering SCSS!

Until next time!


Day 39: Cascade!


CSS, or Cascading Style Sheets, were invented to improve the presentation of the World Wide Web by Håkon Wium Lie. With CSS, Web Developers can add animations, manipulate text, use an image as a background, and much more. The possibilities with CSS are almost boundless. The end product really just depends on the preferences of the Designer/Developer.

There are many ways to invoke CSS. Within html documents, CSS rule-sets can be invoked inline, by using the style element. External style sheets can be invoked by using the @import rule, within the style element. The most common application of CSS is through external style sheets using the link element. CSS can be used with multiple style sheets and a mix of all the aforementioned methods, hence “Cascading” in the name. It uses a weight system to determine which rules to use.


Rule-sets, in CSS, are composed of selectors, properties, and their respective values. Selectors reference the html element to be modified. Properties declare the characteristic of the selector is to be changed. The values define how the property is modified.

I have used CSS for a long time, but it wasn’t until recently that I decided to fill in the gaps of my knowledge. In my pursuit of one day being a 10x Engineer, I have really enjoyed using shorthand CSS properties. There is so much to learn with CSS and I’m excited to continue learning about it. I’ll be getting into SASS and advanced CSS in future post!

Until next time!


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!