mnyrop

How I think about Omeka, CollectionBuilder, and Wax

(the messy version)

Tl;dr

• the more you move to spreadsheets, text editors, and the command line from applications with admin interfaces:
  • the more control you get!
  • the more work + thinking you need to put in to the workflow and how it will include your collaborators
• sometimes this control is worth it, sometimes it isn't; it depends on your goals + resources.
• minimal computing isn't about purity politics! it's a provocation to clarify your goals and consider alternative tools and methods to best suit the goals and resources you have.

beesandbombs

// gif by dave aka @beesandbombs :)

int[][] result;
float t, c;

float ease(float p) {
  return 3*p*p - 2*p*p*p;
}

float ease(float p, float g) {

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

nickloewen

This is a plain-text version of Bret Victor’s reading list. It was requested by hf on Hacker News.

---

Highly recommended things!

This is my five-star list. These are my favorite things in all the world.

A few of these works have had an extraordinary effect on my life or way of thinking. They get a sixth star. ★

dansinker

#encoding: UTF-8

require 'rubygems'

require "pismo"
require 'punkt-segmenter'
require 'htmlentities'
require './markov.rb'

CLEAN_TEXT = <<-EOF

gordonbrander

/*
n-vector.js

Copyright (c) 2014 Gordon Brander
Released under the MIT license
http://opensource.org/licenses/MIT

Generic, efficient JavaScript vector math using ordinary arrays
or indexed objects.

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

rakhmad

Setting Up Clojure on OS X

I spent a lot of time trying to find a pretty optimal (for me) setup for Clojure… at the same time I was trying to dive in and learn it. This is never optimal; you shouldn't be fighting the environment while trying to learn something.

I feel like I went through a lot of pain searching Google, StackOverflow, blogs, and other sites for random tidbits of information and instructions.

This is a comprehensive "what I learned and what I ended up doing" that will hopefully be of use to others and act as a journal for myself if I ever have to do it again. I want to be very step-by-step and explain what's happening (and why) at each step.

Step 1: Getting Clojure (1.3)

avoine

#!/usr/bin/env python
# -*- coding: utf-8 -*-

import sys
import csv
from optparse import OptionParser

import urllib
import httplib
import urlparse

etrepat

{
	// Sets the colors used within the text area
	"color_scheme": "Packages/Color Scheme - Default/Monokai.tmTheme",

	// Note that the font_face and font_size are overriden in the platform
	// specific settings file, for example, "Base File (Linux).sublime-settings".
	// Because of this, setting them here will have no effect: you must set them
	// in your User File Preferences.
	"font_face": "Monaco",
	"font_size": 12,