mattsah

<?php namespace Redub\Base {

	class Person extends \Redub\ORM\Model
	{

		/**
		 * Fetch the values of the related groups from the database
		 *
		 * @access public
		 * @return Collection The groups values

mattsah

<?php


function ★() {
	echo "You're a star! \n";
}

★();

mattsah

$config = preg_replace('#=>\s*array \(#', '=> [', $config);
$config = preg_replace('#\),#', '],', $config);
$config = preg_replace('#,(\s*)\]#', '$1]', $config);
$config = preg_replace('#\d+ => #', '', $config);
$config = preg_replace('#\[\s+\]#', '[]', $config);
$config = str_replace('  ', "\t", $config);

mattsah

	'/test/[!:name]'      => function($this) {
		if ($this['request']->checkMethod('get')) {
			return strtoupper($this['request']->get('name'));
		}
	}

mattsah

<% namespace Dotink\Inkwell\View {

	/**
	 *
	 * @author Matthew J. Sahagian [mjs] <[email protected]>
	 * @param $users The array of users
	 * @param
	 */

	if ($this['wtf'] == 'test'):

mattsah

<?php namespace Dotink\Jest {

  include 'Mime.php';

	Mime::define('App\Test')->implementing('IFake')
		-> extending('App\TestBase')->implementing('IFakeBase');

	$test = Mime::create('App\Test')
		-> onNew('factory', function($mime) {
			$mime -> onCall('speak') -> give(function(){

mattsah

<?php namespace Dotink\Jest {

  class Mime extends Jest
	{
		/**
		 *
		 */
		static private $parents = array();

mattsah

<?php

$tests = [
	'FavoriteURL',
	'URLHelper',
	'FavoriteURLs',
	'AmazingURLsFromSpace',
	'FavoriteURLHelper',
	'FBIManBob',
	'removeXMLTags',

mattsah

	\Dotink\Flourish\

		# Loaded from /includes/lib/flourish via:
		#
		# 'autoloaders' => array(
		#     '\Dotink\Flourish\*' => 'COMPAT:includes/lib/flourish'
		# )

		ORM
		ActiveRecord

mattsah

REST is software design on the scale of decades: every detail is intended to promote software longevity and independent evolution. Many of the constraints are directly opposed to short-term efficiency. Unfortunately, people are fairly good at short-term design, and usually awful at long-term design. Most don’t think they need to design past the current release. There are more than a few software methodologies that portray any long-term thinking as wrong-headed, ivory tower design (which it can be if it isn’t motivated by real requirements).