Nathan Kleekamp NathanKleekamp

## resources.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                NathanKleekamp
                / resources.md
            
            
              Created
              July 2, 2013 21:22
                — forked from bobholt/resources.md
            
          
    This is a work in progress. If I missed something or someone, please let me know!
Best Practices

It's hard to recommend best practices in general without context, but basically, writing clean, readable code with lots of comments, and doing a lot of automated unit testing, followed by an automated build process using ANT or Grunt to concatenate and minify files is a start.
Twitter

I don't focus much on blogs any more. I focus more on Twitter. If the people I follow there recommend something, I'll go read it. Here's the best of my Twitter list, including developers, conferences, and interesting groups. There are other great developers on Twitter, but these tweet mostly about development:
Developers


Ben Alman


## node-and-npm-in-30-seconds.sh
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://npmjs.org/install.sh | sh

## frontendDevlopmentBookmarks.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                NathanKleekamp
                / frontendDevlopmentBookmarks.md
            
            
              Created
              June 12, 2014 01:05
                — forked from dypsilon/frontendDevlopmentBookmarks.md
            
          
    Frontend Development

Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.


## 0_reuse_code.js
// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

## The Technical Interview Cheat Sheet.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                NathanKleekamp
                / The Technical Interview Cheat Sheet.md
            
            
              Last active
              August 25, 2015 22:01
                — forked from tsiege/The Technical Interview Cheat Sheet.md
            
              
                This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.
              
          
    Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics.  It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth.  It also will be available as a gist on Github for everyone to edit and add to.
Data Structure Basics

###Array
####Definition:

Stores data elements based on an sequential, most commonly 0 based, index.
Based on tuples from set theory.


## curl-ip-address
# Via http://askubuntu.com/questions/95910/command-for-determining-my-public-ip

curl -s checkip.dyndns.org | sed -e 's/.*Current IP Address: //' -e 's/<.*$//'

## uri.js
var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"

## Wordpress RSS 2.0 image enclosure
function feedFilter($query) {
	if ($query->is_feed) {
		add_filter('rss2_item', 'feedContentFilter');
		}
	return $query;
}
add_filter('pre_get_posts','feedFilter');

function feedContentFilter($item) {


## git.migrate
#!/bin/bash
# Sometimes you need to move your existing git repository
# to a new remote repository (/new remote origin).
# Here are a simple and quick steps that does exactly this.
#
# Let's assume we call "old repo" the repository you wish
# to move, and "new repo" the one you wish to move to.
#
### Step 1. Make sure you have a local copy of all "old repo"
### branches and tags.

## twitter-timline.html
<html>
  <head>
    <title>Twitter User Timeline Widget</title>
    <script>
      // I found Twitter's documentation for the user timeline a bit difficult
      // to follow. Here's a very basic working example for others who might
      // also struggle with it

      // First, include the twitter wiget.js before anything that might require
      // it. The docs recommend including it directly in the page template
	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://npmjs.org/install.sh \| sh
	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console
	# Via http://askubuntu.com/questions/95910/command-for-determining-my-public-ip

	curl -s checkip.dyndns.org \| sed -e 's/.Current IP Address: //' -e 's/<.$//'
	var parser = document.createElement('a');
	parser.href = "http://example.com:3000/pathname/?search=test#hash";

	parser.protocol; // => "http:"
	parser.hostname; // => "example.com"
	parser.port; // => "3000"
	parser.pathname; // => "/pathname/"
	parser.search; // => "?search=test"
	parser.hash; // => "#hash"
	parser.host; // => "example.com:3000"
	function feedFilter($query) {
	if ($query->is_feed) {
	add_filter('rss2_item', 'feedContentFilter');
	}
	return $query;
	}
	add_filter('pre_get_posts','feedFilter');

	function feedContentFilter($item) {
	#!/bin/bash
	# Sometimes you need to move your existing git repository
	# to a new remote repository (/new remote origin).
	# Here are a simple and quick steps that does exactly this.
	#
	# Let's assume we call "old repo" the repository you wish
	# to move, and "new repo" the one you wish to move to.
	#
	### Step 1. Make sure you have a local copy of all "old repo"
	### branches and tags.
	<html>
	<head>
	<title>Twitter User Timeline Widget</title>
	<script>
	// I found Twitter's documentation for the user timeline a bit difficult
	// to follow. Here's a very basic working example for others who might
	// also struggle with it

	// First, include the twitter wiget.js before anything that might require
	// it. The docs recommend including it directly in the page template