(by @andrestaltz)
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.
(by @andrestaltz)
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.
The mistakes of the words 'code', 'hacker' and 'hacking' | |
======================================================== | |
As someone who habitually and professionally spends time writing computer programs and web sites using | |
a variety of programming languages, there are a few phrases that irk me as I feel that they poorly | |
represent the joyful, creative experience that is creating systems within a computer. The majority of | |
my issues are based around the associated semantics of the words used. | |
--- | |
'code' - A code is something written to conceal or hide away. it is something that is secret to be | |
broken or discovered. Writing computer programs is primarily a means of expressions of ideas, | |
instructions or intents. These instructions are increasingly written to be more and more legible to |
{-# LANGUAGE OverloadedStrings #-} | |
module Main where | |
import Web.Scotty | |
import Network.Wai.Middleware.RequestLogger(logStdoutDev) | |
import Data.Aeson ( (.:),(.:?),decode,FromJSON(..),Value(..)) | |
import Data.Text.Lazy (pack) | |
import Control.Applicative ((<$>), (<*>)) | |
import qualified Data.ByteString.Lazy.Char8 as BS |
module InventoryItems(Command(..), Event(..), handle) where | |
import Data.Maybe(isJust) | |
type Id = String | |
type Name = String | |
type Amount = Int | |
data Command = CreateInventoryItem Id | |
| RenameInventoryItem Id Name |
;; I wrote this in the Eurostar on my way back from the last lambdanext.eu clojure course. | |
(ns comprehensions | |
(:refer-clojure :exclude [for doseq]) | |
(:require [clojure.core.reducers :as r])) | |
;; borrowed from clojure.core | |
(defmacro ^{:private true} assert-args | |
[& pairs] | |
`(do (when-not ~(first pairs) |
Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications
like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.
open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl
You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html
Most of these guidelines are to match Apple's documentation and community-accepted best practices. Some are derived some personal preference. This document aims to set a standard way of doing things so everyone can do things the same way. If there is something you are not particularly fond of, it is encouraged to do it anyway to be consistent with everyone else.
This document is mainly targeted toward iOS development, but definitely applies to Mac as well.
NSString *foo = @"bar";
*.acn | |
*.acr | |
*.alg | |
*.aux | |
*.bak | |
*.bbl | |
*.bcf | |
*.blg | |
*.brf | |
*.bst |