Visit my blog or connect with me on Twitter
git init
or
Visit my blog or connect with me on Twitter
git init
or
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 |
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
#!/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 |
Create different ssh key according the article Generating SSH keys.
Example:
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 |