Code Archive

Block Delegates

Often I find myself implementing the same delegate protocol over and over. Consider, for example, the Facebook SDK for iOS. I’d like to make lots of requests to the Graph API, and not have a single callback method request:didLoad: in a single class that looks like: -(void)request:(FBRequest*)request didLoad:(id)result { if (request == mainRequest) { // handle result } else if (request == subRequest1) { // handle result } else if (request == anotherRequest) { // handle result } //.

Less is More :(

The majority of work I do, as a programmer who wears a shirt and tie, involves databases. And I try to keep things nice and simple when working with databases. What I mean by simple is, extra tables in a database is fine, even triple the “minimum number” (whatever that is), if they all mostly follow some pattern. Constructing a database schema is then a simple application of the rules devised when designing the pattern, and means there’s not much to think about or have go wrong.

End of WWDC: Let's Party

So I have mehfforted on the blogging for the past couple of days; it started on Wednesday when I decided that I really didn’t have much to talk about (WWDC content being under a certain agreement whereby I can’t tell you the content) so since that took up most of each day, it seemed worthless to post about it. Now it is Sunday night, so I have plenty of content I can tell you about. (This is also the post I am “treating myself to” for successfully upgrading WordPress manually.)

WWDC Day One: Ponies and Steve

Things I learned today: Applied Queuing Theory. The outside queue to WWDC at about 5:30 AM Queues in Practice and Principle. Another shot of the queue Queues and You: A lesson in hidden opportunities. The queue inside Starbucks Queue Participation for Fun and Profit Internal queue friends Time and Distance: A queue-theoretic case study Are we there yet? Escalating Queues to the Next Level Skilled "escalatio" practitioners on the way up Go go go!