westonruter

<?php
/*
Usage:
	cache_fragment_output( 'unique-key', 3600, function () {
		functions_that_do_stuff_live();
		these_should_echo();
	});
*/

function cache_fragment_output( $key, $ttl, $function ) {

simurai

Docs

• Web Docs: DocHub - DevDocs
• All CSS properties
• HTML Elements: Native - Native2 - Simple - HTML5 demos
• Specs
• Can I use
• Should I use
• jQuery -> JS
• Default Font Family
• Shadow DOM selectors - Form Pseudo Elements

olistik

# place this file in ~/.config/terminator/config
[global_config]
  title_transmit_bg_color = "#d30102"
  focus = system
[keybindings]
  reset_clear = <Ctrl>R
  new_tab = <Ctrl>T
  split_horiz = <Ctrl><Shift>E
  split_vert = <Ctrl>E
  close_term = <Ctrl><Shift>W

briancicutti

class Player
  def play_turn(warrior)
    if warrior.feel.enemy?
       warrior.attack!
    else
      if warrior.health < 20 && !taking_damage?(warrior)
        warrior.rest!
      else
        warrior.walk!
      end

njonsson

Someone recently asked the following question in the discussion forum of the Rubyists LinkedIn group: What separates a junior Rails developer from a senior one?

My response follows. Join us at http://www.linkedin.com/groups?gid=120725 to weigh in on this and other topics of interest to Rubyists. As of today there are almost 1,200 members, including numerous movers and shakers in the Ruby and Rails communities.

“Distinguishing between junior and senior people in the Rails world is not so different from making the distinction in other web development environments.

“Junior Rails people have not dealt with scaling issues to the degree that senior people have. Getting a public-facing Rails application to perform under significant stress is more challenging than doing the same with other building materials such as PHP. Senior people know how to performance-test Rails applications, where to look for bottlenecks, and how to eliminate them one after another until performance is acceptable in real conditions. The Ra