polymetis

• plan for code that is easy to delete/replace rather than code that is easy to extend or reuse. As needs change, you're more likely to change the assumptions about what the system should do than in how many ways it should do it. If the code needs extending, it's then easy to replace it with a bit that's easy to extend
• planning for code that is easy to throw away is the best way I've found to properly bake in abstraction and isolation. The question is always "if I take this shit out or change its implementation entirely, do I need to replace anything else?". If the answer is "yes", then you may be leaking into other components. Fix it. turns out when you have that, it's also suddenly easier to reuse code.
• write a prototype of whatever significant task you have to do, and consider it a draft. Use it to figure out requirements or to make your first mistakes in. Throw it away. Try again. As I gain more experience I find my prototypes smaller and individually more solid, but anything where I lack experience t

polymetis

• plan for code that is easy to delete/replace rather than code that is easy to extend or reuse. As needs change, you're more likely to change the assumptions about what the system should do than in how many ways it should do it. If the code needs extending, it's then easy to replace it with a bit that's easy to extend
• planning for code that is easy to throw away is the best way I've found to properly bake in abstraction and isolation. The question is always "if I take this shit out or change its implementation entirely, do I need to replace anything else?". If the answer is "yes", then you may be leaking into other components. Fix it. turns out when you have that, it's also suddenly easier to reuse code.
• write a prototype of whatever significant task you have to do, and consider it a draft. Use it to figure out requirements or to make your first mistakes in. Throw it away. Try again. As I gain more experience I find my prototypes smaller and individually more solid, but anything where I lack experience t

polymetis

defmodule Episode do
    defstruct id: nil, name: nil, video: nil, markdown: nil, post: nil

    def list do
        [
            %Episode{id: "001", post: "271", name: "Introduction and Installing Elixir",              video: "1366",  markdown: "1382"  },
            %Episode{id: "002", post: "275", name: "Basic Elixir",                                    video: "1367",  markdown: "1357"  },
            %Episode{id: "003", post: "280", name: "Pattern Matching",                                video: "14879", markdown: "1413"  },
            %Episode{id: "004", post: "284", name: "Functions",                                       video: "5086",  markdown: "1559"  },
            %Episode{id: "005", post: "298", name: "Mix and Modules",                                 video: "5087",  markdown: "1654"  },

polymetis

#!/usr/bin/perl

# Emacs starter for Emacs mac port

# Thanks to Aquamacs Project and David Reitter

my $args = "";
my $tmpfiles = "";

for my $f (@ARGV) {

polymetis

Contract Killer 3

Revised date: 07/11/2012

Between us [company name] and you [customer name]

Summary:

We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.

polymetis

// This is a peek behind the curtain at @zaarly's epic-fantasy-heavy-metal-themed internal styleguide, better known as Hammer.
//
// Altering this a bit for my own purposes
//
// With this, you can add the .fancy class to a symbolset span inside of a heading tag to add a nice circular background. 
// Some adjustments to the positioning of a particular glyph may be necessary. 
// Each :before is set to postion: relative, so fine-tuning a .fancy glyph is simple, and won't affect the position of the circle.
//
// Example markup (in HAML):
// %h1

polymetis

# Two things are important to note: 
#
# 1) The code is fugly, because it was a JavaScript/iPad experiment. 
#    I know that it is ugly, so pretty please don't comment on that part.
# 2) I tried to use as many CoffeeScript features as possible,
#    including but not limited to list comprehensions,
#    heredocs, destructuring assignment and also the "do" operator
#
# I welcome comments about stuff that is not CoffeeScripty enough, or what I should
# write differently.

polymetis

/*
 * Customize Footnotify on your site by adding custom css.
 * 
 * This file is NOT loaded by the script and must be
 * implemented on the site in order to apply.
 *
 * More info: https://gist.github.com/1046538
 *
 */