tapi

//
//  NSObject+SMDictionaryMapping.h
//  SoundTrack
//
//  Created by Paddy O'Brien on 12-04-24.
//  Copyright (c) 2012 Paddy O'Brien. All rights reserved.
//

#import <Foundation/Foundation.h>

piscisaureus

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

tapi

#########################
# .gitignore file for Xcode4 / OS X Source projects
#
# Version 2.0
#    For latest version, see: http://stackoverflow.com/questions/49478/git-ignore-file-for-xcode-projects
#
# 2013 updates:
#    - fixed the broken "save personal Schemes"
#
# NB: if you are storing "built" products, this WILL NOT WORK,

chriseidhof

- (NSManagedObjectContext*)managedObjectContextForTesting {
  NSURL *modelURL = [[NSBundle mainBundle] URLForResource:@"YourModelName" withExtension:@"momd"];
  NSManagedObjectModel* model = [[NSManagedObjectModel alloc] initWithContentsOfURL:modelURL];
  NSPersistentStoreCoordinator* coordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:model];
  [coordinator addPersistentStoreWithType:NSInMemoryStoreType configuration:nil URL:nil options:nil error:NULL];
  NSManagedObjectContext* managedObjectContext= [[NSManagedObjectContext alloc] init];
  managedObjectContext.persistentStoreCoordinator = coordinator;
  return managedObjectContext;
}

coffeemug

After spending the better part of the month implementing date support
in RethinkDB, Mike Lucy sent the team the following e-mail. It would
have been funny, if it didn't cause thousands of programmers so much
pain. Read it, laugh, and weep!

-----

So, it turns out that we're only going to support dates between the
year 1400 and the year 10000 (inclusive), because that's what boost
supports.

jspahrsummers

Use cases

1. Turning an eager, pure computation into a lazy one: RACSequence, RACSignal
2. Side-effecting work that is safe to perform multiple times: RACSignal, RACCommand
3. Side-effecting work that is safe to perform multiple times serially, but not concurrently: RACCommand, RefCount()
   • RACScheduler would seem to apply here, but execution could become interleaved and thus not serial
4. Side-effecting work that should only be performed once, then memoized: RACMulticastConnection with a RACReplaySubject, RACSequence
5. Enabling/disabling a UI based on whether work can be performed: RACCommand, RACReplaySubject
   • Replaying is a Good Idea™ because this information may arrive before the UI is ready for it
6. Updating a UI with information about work in progress: RACCommand, RACSubject

jspahrsummers

MVVM example

For a command that initiates a network request when:

• The network connection is up (precondition)
• The network request is not already in progress (enforced serialization)

The lifecycle proceeds as follows:

1. The view model exposes the command and describes its behavior

jerryhjones

//
//  NSObject+TypeValidation.h
//
//  Created by Jerry Jones on 5/15/12.
//  Copyright (c) 2012 Spaceman Labs, LLC. All rights reserved.
//

#import <Foundation/Foundation.h>

BOOL CFTypeIsNull(id object);

jvns

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

landonf

Xcode Wish List:

Legacy Support

• Additional optional downloads:
  • Older SDKs, eg, for building ancient projects.
  • Older compilers (for same).
• Either ship gcc/llvm-gcc or don't. Don't ship clang and call it 'gcc', that just breaks anyone who actually needs GCC and finds your not-gcc in the PATH.

UX

Project/File Navigation