Skip to content

Instantly share code, notes, and snippets.

View brianzelip's full-sized avatar

Brian Zelip brianzelip

View GitHub Profile
echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc
. ~/.bashrc
mkdir ~/local
mkdir ~/node-latest-install
cd ~/node-latest-install
curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1
./configure --prefix=~/local
make install # ok, fine, this step probably takes more than 30 seconds...
curl https://www.npmjs.org/install.sh | sh
@brianzelip
brianzelip / multiple_ssh_setting.md
Created November 1, 2015 19:42 — forked from RomuloOliveira/multiple_ssh_setting.md
Configure multiple git accounts on same computer using ssh

Multiple SSH Keys settings for different github account

Create different public key

Create different ssh key according the article Generating SSH keys.

Example:

@brianzelip
brianzelip / TAGS to json.md
Last active November 7, 2015 19:56
Convert TAGS data to json using Node.js

How to convert data in a TAGS (Twitter Archiving Google Sheet) Archive sheet to json using a Node.js CLI tool

Assumptions with these instructions:

  • you've already got your copy of the TAGS Google Spreadsheet set up working with your Twitter dev account
  • install Node.js (and its package manager NPM which allows you to quickly install modular Node packages that perform specific tasks). NPM is included when you install Node. Read how to quickly install Node on your operating system on this NPM blog post. If you don't already have Node set up, I think it's a good idea to do so because it provides a wide range of software tools that do one job well (usually). Very applicable to all sorts of needs from digital humanities, to bio informatics, to web dev and more.

  1. Open your command line and install the Node package csv2json.
{
"html": {
"filters": "html",
"profile": "html",
"snippets": {
"!": "<!DOCTYPE html>\n<html lang=\"en-US\">\n\n\t<head>\n\t\t<meta charset=\"UTF-8\">\n\t\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\t\t<meta http-equiv=\"X-UA-Compatible\" content=\"IE=edge,chrome=1\">\n\t\t<link rel=\"stylesheet\" href=\"/css/index.css\">\n\t\t<title>${1:TITLE}</title>\n\t\t<meta name=\"description\" content=\"\">\n\t\t<meta name=\"author\" content=\"Brian Zelip\">\n\t\t<meta name=\"keywords\" content=\"\">\n\t</head>\n\n\t<body>\n\n\t\t\n\n\t</body>\n\n</html>\n"
},
"abbreviations": {
"scripts": "<script src=\"\">"
}
@brianzelip
brianzelip / fix_homebrew.rb
Created March 26, 2016 15:19 — forked from rpavlik/fix_homebrew.rb
Fix permissions on /usr/local for Homebrew
#!/usr/bin/ruby
#
# This script fixes /usr/local only.
#
# 6th January 2010:
# Modified the script to just fix, rather than install. - rpavlik
#
# 30th March 2010:
# Added a check to make sure user is in the staff group. This was a problem
# for me, and I think it was due to me migrating my account over several
@brianzelip
brianzelip / scalable-css-draft.md
Created March 31, 2016 17:43 — forked from mrmrs/scalable-css-draft.md
WIP thoughts on my last few years thinking about how to scale css for large and small teams working on large and small web applications.

How not to scale css

Several years ago I got curious about how css worked at scale. When I first started out, there weren’t nearly as many learning resources as there are now. CSS zen garden was amazing, at the time it showed how much you could change a design without altering the html.

In the beginning, that’s what people sold me as a feature. By writing css, you could make a change one place and have it propagate everywhere. In principle this sounds pretty good. I’m lazy so I like doing things one time. But eleven years later, my experience on both large and small teams is that this is the most terrifying thing about css.

https://twitter.com/thomasfuchs/status/493790680397803521

In the past few years a lot of very smart people have been thinking more about CSS and this has lead to some fascinating discussions around how to build ‘scalable’ ui and how that relates to CSS. When I first started to think about scalability I naturally started to read every blog post and watch every tech talk I could get

@brianzelip
brianzelip / soma.txt
Created December 6, 2016 23:28 — forked from andreis/soma.txt
Soma Radio iTunes Playlist
Name Artist Composer Album Grouping Work Movement Number Movement Count Movement Name Genre Size Time Disc Number Disc Count Track Number Track Count Year Date Modified Date Added Bit Rate Sample Rate Volume Adjustment Kind Equalizer Comments Plays Last Played Skips Last Skipped My Rating Location sonicuniverse-192-mp3 11/1/16, 1:44 PM 192 44100 Internet audio stream 1 11/1/16, 1:44 PM http://ice1.somafm.com/sonicuniverse-192-mp3 beatblender-128-aac 11/1/16, 1:45 PM 44100 Internet audio stream 1 11/1/16, 1:45 PM http://ice1.somafm.com/beatblender-128-aac suburbsofgoa-128-mp3 11/1/16, 1:45 PM 128 44100 Internet audio stream 1 11/1/16, 1:45 PM http://ice1.somafm.com/suburbsofgoa-128-mp3 thetrip-128-mp3 11/1/16, 1:46 PM 128 44100 Internet audio stream 1 11/1/16, 1:46 PM http://ice1.somafm.com/thetrip-128-mp3 7soul-128-aac 11/1/16, 1:48 PM 44100 Internet audio stream 1 11/1/16, 1:48 PM http://ice1
@brianzelip
brianzelip / NCBI-Hackathons-products-checklist.md
Last active August 28, 2017 19:40
Marketing checklist for NCBI hackathons

NCBI hackathon product checklist

In order to maintain the online list of products created at NCBI hackathons, each shipped product's repo should include the following:

  • Title (required) - the proper display title for the product, with no unnecessary underscores/hyphens/lack of whitespace/etc., e.g., "NCBI Computational Cookbook", not "NCBIComputationalCookbook" or "NCBI_Computational_Cookbook"; achieve this via one of two methods:
    1. the repo name itself, ONLY IF it is the string of the ideal product name for display purposes, or,
    2. an issue titled title, with a label titled metadata, and the body of which should contain only the human readable title string for display purposes; see NCBI-Hackathons/ncbi-hackathons.github.io#5
  • Description (required) - the proper display description for the product, with proper grammer/punctuation/capitalization/etc.; achieve this via one of two methods:
  1. the repo description as input on the repo's homepage, above the list o