C nguyenchiencong

## scraper.rb
#!/usr/bin/env ruby
require 'capybara'
require 'capybara/poltergeist'

class Scraper
  include Capybara::DSL
  Capybara.register_driver :poltergeist do |app|
    Capybara::Poltergeist::Driver.new app,
      phantomjs_options: ['--load-images=no','--ignore-ssl-errors=yes'],
      js_errors: false,

## hidemyass_proxylist.py
#! /usr/bin/env python
# -*- coding: utf-8 -*-
from __future__ import absolute_import, print_function, unicode_literals
__docformat__ = 'reStructureText'
import logging
import re
import sys

import html5lib
from xml.etree.ElementTree import tostring

## application.html.erb
<!DOCTYPE html>
<html>
  <head>
    <!-- (...) -->
    <%= csrf_meta_tag unless response.cache_control[:public] %>
    <!-- (...) -->
  </head>
  <body>
    <!-- (...) -->
    <% unless response.cache_control[:public] %>

## gist:9637834

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                nguyenchiencong
                / gist:9637834
            
            
              Created
              March 19, 2014 08:46
                — forked from ryansobol/gist:5252653
            
          
    Originally published in June 2008
When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first.  In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written.  And in the corporate/enterprise world, I often don't have access to their previous work.
To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.
What to expect

Candidates will typically give you a range of responses based on their experience and personality.  So it's up to you to decide the correctness of their answer.

  
## nginx.conf
# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

## default.vcl.pl
# https://www.varnish-cache.org/docs/2.1/tutorial/vcl.html
# https://www.varnish-cache.org/trac/wiki/VCLExamples

# Summary
# 1. Varnish will poll the backend at /health_check to make sure it is
#    healthy. If the backend goes down, varnish will server stale content
#    from the cache for up to 1 hour.
# 2. Varnish will pass X-Forwarded-For headers through to the backend
# 3. Varnish will remove cookies from urls that match static content file
#    extensions (jpg, gif, ...)

## pedantically_commented_playbook.yml
---
# ^^^ YAML documents must begin with the document separator "---"
#
#### Example docblock, I like to put a descriptive comment at the top of my
#### playbooks.
#
# Overview: Playbook to bootstrap a new host for configuration management.
# Applies to: production
# Description:
#   Ensures that a host is configured for management with Ansible.

## dblink-demo
[~/src] heroku apps:create dblink-demo
Creating dblink-demo... done, stack is cedar
http://dblink-demo.herokuapp.com/ | git@heroku.com:dblink-demo.git
[~/src] heroku addons:add heroku-postgresql:dev -a dblink-demo
Adding heroku-postgresql:dev on dblink-demo... done, v3 (free)
Attached as HEROKU_POSTGRESQL_IVORY_URL
Database has been created and is available
 ! This database is empty. If upgrading, you can transfer
 ! data from another database with pgbackups:restore.
Use `heroku addons:docs heroku-postgresql:dev` to view documentation.
	#!/usr/bin/env ruby
	require 'capybara'
	require 'capybara/poltergeist'

	class Scraper
	include Capybara::DSL
	Capybara.register_driver :poltergeist do \|app\|
	Capybara::Poltergeist::Driver.new app,
	phantomjs_options: ['--load-images=no','--ignore-ssl-errors=yes'],
	js_errors: false,
	#! /usr/bin/env python
	# -- coding: utf-8 --
	from __future__ import absolute_import, print_function, unicode_literals
	__docformat__ = 'reStructureText'
	import logging
	import re
	import sys

	import html5lib
	from xml.etree.ElementTree import tostring
	<!DOCTYPE html>
	<html>
	<head>
	<!-- (...) -->
	<%= csrf_meta_tag unless response.cache_control[:public] %>
	<!-- (...) -->
	</head>
	<body>
	<!-- (...) -->
	<% unless response.cache_control[:public] %>
	# to generate your dhparam.pem file, run in the terminal
	openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048
	# https://www.varnish-cache.org/docs/2.1/tutorial/vcl.html
	# https://www.varnish-cache.org/trac/wiki/VCLExamples

	# Summary
	# 1. Varnish will poll the backend at /health_check to make sure it is
	# healthy. If the backend goes down, varnish will server stale content
	# from the cache for up to 1 hour.
	# 2. Varnish will pass X-Forwarded-For headers through to the backend
	# 3. Varnish will remove cookies from urls that match static content file
	# extensions (jpg, gif, ...)
	---
	# ^^^ YAML documents must begin with the document separator "---"
	#
	#### Example docblock, I like to put a descriptive comment at the top of my
	#### playbooks.
	#
	# Overview: Playbook to bootstrap a new host for configuration management.
	# Applies to: production
	# Description:
	# Ensures that a host is configured for management with Ansible.
	[~/src] heroku apps:create dblink-demo
	Creating dblink-demo... done, stack is cedar
	http://dblink-demo.herokuapp.com/ \| git@heroku.com:dblink-demo.git
	[~/src] heroku addons:add heroku-postgresql:dev -a dblink-demo
	Adding heroku-postgresql:dev on dblink-demo... done, v3 (free)
	Attached as HEROKU_POSTGRESQL_IVORY_URL
	Database has been created and is available
	! This database is empty. If upgrading, you can transfer
	! data from another database with pgbackups:restore.
	Use `heroku addons:docs heroku-postgresql:dev` to view documentation.