mattorb

// keyTimes = array floats for second [(NSNumber)1.2,(NSNumber)2.0] == 2 frames, 1.2 secs for first frame, 2.0 seconds for second frame
- (void) addDiscreteTimedImageAnimation:(NSString *)animationName view:(UIImageView *)imageView images:(NSArray *)images keyTimes:(NSArray *)keyTimes repeatCount:(float)repeatCount onDone:(SEL)callback {
	CAKeyframeAnimation *animation = [CAKeyframeAnimation animationWithKeyPath:@"contents"];
	NSMutableArray *values = [[NSMutableArray alloc] initWithCapacity:[images count]];
	NSMutableArray *keyTimesAsPercent = [[NSMutableArray alloc] initWithCapacity:[keyTimes count]];
	double totalDuration = 0.0;
	
	for(UIImage *image in images) {
		[values addObject:(id)(image.CGImage)];
	}

erikh

#!/usr/bin/env sh

##
# This is script with usefull tips taken from:
#   https://github.com/mathiasbynens/dotfiles/blob/master/.osx
#
# install it:
#   curl -sL https://raw.github.com/gist/2108403/hack.sh | sh
#

1wErt3r

;SMBDIS.ASM - A COMPREHENSIVE SUPER MARIO BROS. DISASSEMBLY
;by doppelganger (doppelheathen@gmail.com)

;This file is provided for your own use as-is.  It will require the character rom data
;and an iNES file header to get it to work.

;There are so many people I have to thank for this, that taking all the credit for
;myself would be an unforgivable act of arrogance. Without their help this would
;probably not be possible.  So I thank all the peeps in the nesdev scene whose insight into
;the 6502 and the NES helped me learn how it works (you guys know who you are, there's no 

paul-delange

//
//  GIFDownloader.h
//  TheJoysOfCode
//
//  Created by Bob on 29/10/12.
//  Copyright (c) 2012 Tall Developments. All rights reserved.
//

#import <Foundation/Foundation.h>

brentsimmons

@implementation UITextView (RSExtras)


static BOOL stringCharacterIsAllowedAsPartOfLink(NSString *s) {

    /*[s length] is assumed to be 0 or 1. s may be nil.
     Totally not a strict check.*/

    if (s == nil || [s length] < 1)
        return NO;

chrismiles

""" File: reveal.py

Add to ~/.lldbinit:
    command script import ~/.lldb-scripts/reveal.py

Q: Want to automatically load the Reveal lib on launch while debugging from Xcode?
A: In Xcode:
    Add a Symbolic Breakpoint
    Symbol: "UIApplicationMain"
    Action: Debugger Command with value "reveal"

raven

<?xml version="1.0" encoding="UTF-8"?>
<Bucket
   type = "2"
   version = "2.0">
   <Breakpoints>
      <BreakpointProxy
         BreakpointExtensionID = "Xcode.Breakpoint.SymbolicBreakpoint">
         <BreakpointContent
            shouldBeEnabled = "Yes"
            ignoreCount = "0"

NSUserDefaults is kinda like git

Note that like all analogies, this is not a perfect one. I find it helps me think about it though. Also, don't try to draw conclusions about performance from this analogy :)

-[NSUserDefaults setObject:forKey:] is like...
<edit file to add key and value>
git add file
git commit
dispatch_after(some time, dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0), ^{
    [[NSUserDefaults standardUserDefaults] synchronize]
});

mattt

struct もじれつ: Printable {
    let description: String

    init(string: String) {
        var mutableString = NSMutableString(string: string) as CFMutableString
        if CFStringTransform(mutableString, nil, kCFStringTransformLatinHiragana, 0) == 1 {
            self.description = mutableString as NSString
        } else {
            self.description = string
        }

gist:8a163db3f7f3d81d5296

Your goals are to reduce the number of things that you have to keep in your head at any given moment, and to rely as little as possible on your own ability to consistently do things right.
If you make a thing immutable ('let' in swift), you never have to think about what happens if it changes, or what other parts of the code you'll effect if you change it.
If you split complex functions into several smaller functions that only interact by passing arguments or getting return values, then you limit the amount of code you need to consider when hunting for a bug, and you can test each small piece separately.
If you understand what things must be true in your code (aka invariants, for example "a person's age must be greater than 0"), and either provide no function that can cause them to be untrue, or check and crash immediately when they're untrue, then you don't have to debug issues caused by incorrect assumptions.
If you remove possibilities (for example, Swift removes the possibility of things being nil unless