I debated about what to write about today, especially in the wake of yesterday’s WWDC ticket frenzy, the subsequent online screaming about it, and everything else. I think in the end, Apple will do what Apple does, and that’ll be … Continue reading →
How do you know if your code works? You test it of course. But, how do you test your code? Do you run it in the simulator? On your device? Is that enough? The simple answer is: No. How can … Continue reading →
What is the cost of expedience? Answer: Technical debt. How often have you had to solve a problem quickly, knowing that your solution was correct (i.e. it works), but not really how you’d have liked to do it? Sometimes the … Continue reading →
I made a stupid mistake recently, which cost me more than a few hours of time to figure out. But I learned a couple things: Xcode will let you dig as deep a hole as you like, despite its “assistance”, … Continue reading →
It turns out that building multiple targets from one source code base is both easy and hard, both simple and complex. It all depends not only on the ultimate products you want to create, but a bit on your workflow … Continue reading →
Several months ago I wrote about some tricks I was using to build many targets from one code base. The rubber is meeting the road on that project as we get closer to being ready to submit to Apple, and … Continue reading →
Set aside any ideas you may have that global data is evil. If you spend any time on the StackOverflow website, you’ve likely seen questions like “How do I share data from one view controller with another view controller?” The … Continue reading →