2014-04-03 21:45:06.656 xcodebuild[9999:1007] [MT] PluginLoading: Required plug-in compatibility UUID A2E4D43F-41F4-4FB9-BB94-7177011C9AED for plug-in at path '~/Library/Application Support/Developer/Shared/Xcode/Plug-ins/CodePilot3.xcplugin' not present in DVTPlugInCompatibilityUUIDs
Build settings from command line:
DSTROOT = build
INSTALL_PATH = /bin
OTHER_CFLAGS = '-DCOMPILE_TIME_DEFAULT_TEMPLATE_PATH=@"/usr/local/Cellar/appledoc/2.2-963/Templates"'
SYMROOT = build
=== CLEAN TARGET appledoc OF PROJECT appledoc WITH CONFIGURATION Release ===
Big Data surveys of the Mobile Marketplace.
PBS: Why we're not doing Android yet.
Jury: App Store Pricing, Part 1.
If your Unit Tests break, be sure to check out this link.
It usually means there's a non-included Pods configuration set in your Debug build. Be sure to scroll down for further information if you really need to look.
It might also be helpful to reference the Podfile depency declarations page just in case you've got to do some Podfile (or Pod) hacking.
Finally, don't forget to make sure the libPods.a file is added as a linked library to the Unit Tests bundle. That could cause problems too if it isn't.
Updating to the latest Oh-My-Zsh commit broke my Agnoster prompt and by extension, my font, Inconsolata-dz for Powerline.
To fix it, I needed to update my Inconsolata-dz for Powerline font.
All I needed to do was download the font and add it to the Mac FontBook.
Hello Gisties!
It's been a while.
So I'm deep in the exploration of what it takes to live sustainably on an exponential change curve.
This isn't even remotely theoretical. Given how I do iOS Consulting (which is competently, but not blindingly fast), it's a struggle to stay über-current, much less on the edge. After being an iOS consultant for over 4-ish years, I can authentically say it's not going to happen accidentally.
Apple this year is doing something very different. They've made all their WWDC session videos available roughly the same day that they were given, along with the PDF slide deck and the source code.
I got to work on RestKit 0.20.0 a little bit with @BlakeWatters back in the winter.
I'm cranking it up again for another set of projects and I noticed that trying to build the default gem set caused a crash.
Here's my environment:
- OS X: 10.8.3
- Xcode: 4.6.2
- Xcode CLI Tools: 4.6.2
- Homebrew-installed
ruby 2.0.0-p0
iCloud has obviously been having some problems. The Key-Value store works well, but the rest of the technology -- not so much.
This gist is really just an exploration of what it could take to actually have workable syncing b/t all the iDevices and Mac clients.
This is a big one. I have a hunch that architecting ANY real syncing solution requires meaningful canonical truth in the sense that you should be able to go to the main server and get the latest (canonical) snapshot of "the state of the world" and then sync against it, reconciling diffs, updating timestamps, etc.
Apple, from what I understand, chose to go with something more peer-to-peer driven. Why? Who knows.
As I've been listening to the Debug podcast, it occurred to me that there was a real experiment that could be undertaken to bring Gamification to political fundraising and volunteering.
One of the things that OFA 2008 and 2012 did was empower groups to engage in fundraising. Also, individuals were empowered to phone-bank and do volunteer organizing at an unprecedented level. But what if that kind of thinking could be brought down to non-POTUS races? Could we actually gamify the big things that draw citizens to participate? And have those things be a way to create access?
You could make a core app or set of apps and then skin them for each candidate. That way the codebase is very reusable and the ideas are scalable.
I think this has some legs.
<?xml version="1.0" encoding="UTF-8"?> | |
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
<plist version="1.0"> | |
<array> | |
<dict> | |
<key>IDECodeSnippetVersion</key> | |
<integer>1</integer> | |
<key>IDECodeSnippetCompletionPrefix</key> | |
<string>@protocol</string> | |
<key>IDECodeSnippetContents</key> |
The phrase "A comma, not a period" comes from Evangelical Christian circles, where the notion of "being finished" is a period and being in progress for the transformation of righteousness is a comma.
Done and Gets Things Smart is an ideal I aspire to. I don't know if I'll ever get to "god-like" seed engineer status (according to Steve Yegge), but I do see a pathway to emulating particles of that superhero engineer (If you want a sample of who I'm talking about, read this book).
A screening interview at Black Pixel I think would look something like Rob Napier's interview.
A serious candidate interview looks exactly like this.
Here's the direction