ddemaree

CREATE TABLE items (
  uuid VARCHAR(255) NOT NULL PRIMARY KEY,
  name VARCHAR(255) NOT NULL DEFAULT '');

CREATE TABLE item_versions (
  uuid VARCHAR(255) NOT NULL PRIMARY KEY,
  version INT(64) NOT NULL UNIQUE AUTO_INCREMENT,
  updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP);

INSERT INTO items(uuid, name) VALUES("APP_GENERATED_ID", "An item");

ddemaree

@interface DDImportOperation

@property (strong, nonatomic) NSPersistentStoreCoordinator *persistentStoreCoordinator;
@property (strong, nonatomic) NSManagedObjectContext *managedObjectContext;

-(void)initWithPersistentStoreCoordinator:(NSPersistentStoreCoordinator*)persistentStoreCoordinator;
-(void)saveChanges;

@end

ddemaree

class ApplicationController < ActionController::Base

  def current_user
    User.find_by_id(session[:user_id])
  end

  def current_user=(user)
    session[:user_id] = user.id
  end

ddemaree

Slides

You can view or download my slides from Speaker Deck: The Weight of the Web (Web Directions South).

Referenced in my talk

• The Typekit Blog - Type study: Hi-DPI web typography by myself. Discusses some type-specific concerns when adapting web design for Retina-class displays, including dealing with overly light typefaces on 1x-resolution screens.
• Karen McGrane's Content Strategy for Mobile from A Book Apart. Discusses adaptive content at some length, including some examples of websites that serve up varied content structures appropriate to each reading context.

ddemaree

This code is extracted/adapted from Mat Brown's Sunspot gem. One of Sunspot's nicest features is an expressive DSL for defining search indexes and performing queries. It works by instance_eval-ing a block you pass into it in the context of its own search builder object. In this code, the pig thing1 statement is roughly equivalent to zoo = Zoo.new; zoo.pig(thing1).

Sunspot's DSL has to resort to trickery: the instance_eval_with_context method uses eval to get the block to give up the object it considers to be self, then sets up an elaborate system of delegates and method_missing calls so any methods not handled by the DSL are forwarded to the surrounding object. But as a result, this syntax is minimal and beautiful, and it works the way you expect whether or not you prefer blocks to yield an object.

Without this trick the block would be restricted to either the original, "calling" context (as a closure) or the DSL's "receiving" context (using instance_eval), but not both.

Using `ins

ddemaree

namespace :spec do
    SPEC_SUITES = %w(models requests integration helpers controllers lib)

    def sample_spec_files(num=5)
      [].tap do |specs|
        SPEC_SUITES.each do |dirname|
          files = Dir[Rails.root.join("spec", dirname, "**", "*_spec.rb")]
          specs.concat files.shuffle.first(num)
        end.shuffle
      end

ddemaree

class Ticket < ActiveRecord::Base

  SEARCH_COLUMNS = {
    :tickets => [:token, :subject, :body, :customer_name, :customer_email],
    :notes   => [:body, :author_name, :author_email]
  }

  def self.conditions_for_keyword_search(table, keywords)
    # Because we may use this string elsewhere, we don't want to mutate the only copy
    query_words = keywords.dup

ddemaree

@mixin retina($ratio: 1.5) {
  $dpi: $ratio * 96;
  $opera-ratio: $ratio * 100;

  @media only screen and (-webkit-min-device-pixel-ratio: #{$ratio}),
         only screen and (     -o-min-device-pixel-ratio: '#{$opera-ratio}/100'),
         only screen and (                min-resolution: #{$dpi}dpi),
         only screen and (                min-resolution: #{$ratio}dppx) {
    @content;
  }

ddemaree

No More Masters

In my book Git for Humans, published in 2016, I made copious references to master as the primary branch name used in Git repositories.

The term master can refer to a "master copy," meaning the original or canonical version of something from which other copies are made. But its primary meaning in the English language is "a person who has general authority over others." And, especially in American and British English, it's hard to separate the word "master," and that meaning of it, from another related word: "slave."

If we're being honest, folks in tech have known that "master" and "slave" are problematic terms for a while, even if they haven't felt motivated to change them. There are those who say that if these words refer to objects or systems, rather than people, then they can't be offensive, just as people argue that tech is a meritocracy and algorithms can't be biased. These argument

ddemaree

// First, we must import the schema creator
import createSchema from "part:@sanity/base/schema-creator";

// Then import schema types from any plugins that might expose them
import schemaTypes from "all:part:@sanity/base/schema-type";

// We import object and document schemas
import blockContent from "./blockContent";
import category from "./category";
import post from "./post";