tlberglund

#!/usr/bin/ruby

#
# See https://github.com/soffes/hue for deets on the API. This script requires
# the Gem be installed, which is documented at the same URL.
#

require 'hue'

my.css

background: linear-gradient(183deg, #f47b51, #ee497c, #671d81);
background-size: 600% 600%;
-webkit-animation: bg-gradient-change 11s ease infinite;
-moz-animation: bg-gradient-change 11s ease infinite;
-o-animation: bg-gradient-change 11s ease infinite;
animation: bg-gradient-change 11s ease infinite;
@-webkit-keyframes bg-gradient-change {
    0%{background-position:0% 51%}
    50%{background-position:100% 50%}
    100%{background-position:0% 51%}

helenvholmes

#!/bin/bash

echo "Title of post:"
read title

echo "Description of post:"
read description

echo "Tag post:"
read tags

nickh

Myth of a Christian Nation

Pre Thoughts

• Christianity is a myth: there is only individual interpretations of what has been passed down, influenced by history and culture. It's not possible to say that one is the "right" version. (Also see The Myth of the Christian Religion.)
• Myth that US was originally a religious nation vs a secular nation with freedom of thought populated by a high % of Christians.
• Myth that Christianity now is the same as it was in the 1700s.
• Myth that Christianity was ever intended to be a political force.

bkeepers

#!/bin/sh
#
# Requires the `t` gem: https://github.com/sferik/t
#
#    gem install t
#

if [ -z $(t lists | grep -i githubbers) ] 
then
  t list create GitHubbers

jglovier

My SCSS Style Guide

One of the beauties of authoring code is that apart from basic syntax rules, formatting is flexible. But we all know there are best practices for helping make certain code more readable, and more friendly for collaborator environments.

Here's a suggested style guide for authoring SASS files (SCSS flavor specifically) based on my own personal experience. You may like what I've come up with (then use it), or you may not like it (then fork it). Either way I hope it gets you to think more critically about how formatting your code can lead to efficiency for yourself, and for your team.

// Style category name
// -------------------------------------------/

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

endolith

ּ_בּ
בּ_בּ
טּ_טּ
כּ‗כּ
לּ_לּ
מּ_מּ
סּ_סּ
תּ_תּ
٩(×̯×)۶
٩(̾●̮̮̃̾•̃̾)۶