Ray Ch iraycd

## pagination.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                iraycd
                / pagination.md
            
            
              Created
              November 28, 2018 05:49
                — forked from mislav/pagination.md
            
              
                "Pagination 101" by Faruk Ateş
              
          
    Pagination 101

Article by Faruk Ateş, [originally on KuraFire.net][original] which is currently down
One of the most commonly overlooked and under-refined elements of a website is its pagination controls. In many cases, these are treated as an afterthought. I rarely come across a website that has decent pagination, and it always makes me wonder why so few manage to get it right. After all, I'd say that pagination is pretty easy to get right. Alas, that doesn't seem the case, so after encouragement from Chris Messina on Flickr I decided to write my Pagination 101, hopefully it'll give you some clues as to what makes good pagination.
Before going into analyzing good and bad pagination, I want to explain just what I consider to be pagination: Pagination is any kind of control system that lets the user browse through pages of search results, archives, or any other kind of continued content. Search results are the o

  
## index.html
<html>
<body>

<style>
svg {
    width: 100%;
    height: 240px;
}

g text {

## Instructions.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                iraycd
                / Instructions.md
            
            
              Last active
              August 29, 2015 14:15
                — forked from jmdobry/Instructions.md
            
          
    Start your rethinkdb instance with this flag:
--bind all (or bind=all in the configuration file for your instance)
Block external access to the web UI with these two commands:
sudo iptables -A INPUT -i eth0 -p tcp --dport 8080 -j DROP
sudo iptables -I INPUT -i eth0 -s 127.0.0.1 -p tcp --dport 8080 -j ACCEPT
Install nginx:
sudo apt-get install nginx

  
## nodejs-app.conf
description "Upstart script to run a nodejs app as a service"
author "Louis Chatriot"

env NODE_BIN=/usr/local/bin/node
env APP_DIR=/path/to/app/dir
env SCRIPT_FILE="scriptfile.js"   # Entry point for the nodejs app
env LOG_FILE=/path/to/logfile.log
env RUN_AS="anyuser"        # Upstart can only be run nicely as root, need to drop privileges
env SERVER_ENV="anything"   # Usual apps can be run in different environments (development, test, production ...)
                            # I typically use the environment variable NODE_ENV (see below)

## interview-questions.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                iraycd
                / interview-questions.md
            
            
              Last active
              August 29, 2015 13:58
                — forked from jvns/interview-questions.md
            
          
    A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.
I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.
I'd love comments and suggestions about any of these.
I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.
I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

  
## _mixins.scss
@mixin box-shadow($top, $left, $blur, $color, $inset: false) {
  @if $inset {
    -webkit-box-shadow:inset $top $left $blur $color;
    -moz-box-shadow:inset $top $left $blur $color;
    box-shadow:inset $top $left $blur $color;
  } @else {
    -webkit-box-shadow: $top $left $blur $color;
    -moz-box-shadow: $top $left $blur $color;
    box-shadow: $top $left $blur $color;
  }

## example-user.js
  var user = {
    validateCredentials: function (username, password) {
      return (
          (!(username += '') || username === '') ? { error: "No Username Given.", field: 'name' }
        : (!(username += '') || password === '') ? { error: "No Password Given.", field: 'pass' }
        : (username.length < 3)                  ? { error: "Username is less than 3 Characters.", field: 'name' }
        : (password.length < 4)                  ? { error: "Password is less than 4 Characters.", field: 'pass' }
        : (!/^([a-z0-9-_]+)$/i.test(username))   ? { error: "Username contains invalid characters.", field: 'name' }
        : false
      );
	description "Upstart script to run a nodejs app as a service"
	author "Louis Chatriot"

	env NODE_BIN=/usr/local/bin/node
	env APP_DIR=/path/to/app/dir
	env SCRIPT_FILE="scriptfile.js" # Entry point for the nodejs app
	env LOG_FILE=/path/to/logfile.log
	env RUN_AS="anyuser" # Upstart can only be run nicely as root, need to drop privileges
	env SERVER_ENV="anything" # Usual apps can be run in different environments (development, test, production ...)
	# I typically use the environment variable NODE_ENV (see below)
	@mixin box-shadow($top, $left, $blur, $color, $inset: false) {
	@if $inset {
	-webkit-box-shadow:inset $top $left $blur $color;
	-moz-box-shadow:inset $top $left $blur $color;
	box-shadow:inset $top $left $blur $color;
	} @else {
	-webkit-box-shadow: $top $left $blur $color;
	-moz-box-shadow: $top $left $blur $color;
	box-shadow: $top $left $blur $color;
	}
	var user = {
	validateCredentials: function (username, password) {
	return (
	(!(username += '') \|\| username === '') ? { error: "No Username Given.", field: 'name' }
	: (!(username += '') \|\| password === '') ? { error: "No Password Given.", field: 'pass' }
	: (username.length < 3) ? { error: "Username is less than 3 Characters.", field: 'name' }
	: (password.length < 4) ? { error: "Password is less than 4 Characters.", field: 'pass' }
	: (!/^([a-z0-9-_]+)$/i.test(username)) ? { error: "Username contains invalid characters.", field: 'name' }
	: false
	);