Zac Bowling

"WOOT! Thanks!" - Zac Bowling

"I wrote an iPad controlled NXT rover for a hackathon last year. http://zbowling.github.com/NXT..." - Zac Bowling

"This isn't bad. It's much better than what Three20 tried to do by subclassing everything. Giving a good data source wrapper (like NSFetchResultsController does for CoreData) is a good design." - Zac Bowling

"Ok so here is what happens. I'm an iOS developer and have been using this since I was told about it at WWDC for quite a while.  What happens is that it kills all the applications running the background. Clears your memory which may be a bit fragmented. No real magic here. Any perceived "sluggishness" that you had with the home button was just apps hogging CPU time when they are being asked to shutdown or suspend when you hit the home button. Of coursing killing all the background apps in memory may make your CPU feel faster for a minute but it's only temporary. These "OMG, you saved my iPad 2!" posts crack me up a little." - Zac Bowling

"The lite version stuff about upselling to the full version isn't totally right. You show disabled features as they don't hinder usabitly of the app's core features. Like you can show levels you don't have access to yet unless you do in app purchasing or say that you can't access certain features with a "pro" version. Look at hipstamatic and path. purchasable features all over the place." - Zac Bowling

"Hi Matt, I didn't want to draw to much attention around AFNetworking but was looking for a recent example. But on AFNetworking... We have been pushing towards supporting both concepts in the same code and that both goals can't be obtained with the same code without adding to much bloat. We are grinding away constantly in our team but I've pushed it so that we only actually differ on less than a 300 lines of code (if you ignore that we split out AFXMLDocumentRequestOperation which wasn't necessary but made the code easier to read). We need it to work with AFNetworking in both ways. On one end we have big backend for our sync engine that uses NSOperationQueues and goes right into the NSOperation subclasses all over the place to talk back our web-services (and other magic I can't talk about) and then we have frontend code that simply fires off a few requests using AFHTTPClient to a few third party APIs. We are using one unified stack for both (which helps with testing and logging). We..." - Zac Bowling

Posted IMG_2299.MOV Watch on Posterous ... to Zac is geek - Zac Bowling from Posterous

Posted IMG_2300.MOV Watch on Posterous ... to Zac is geek - Zac Bowling from Posterous

Posted ... to Zac is geek - Zac Bowling from Posterous