Storyboards
The eternal question of iOS development: Should you use a Storyboard or program your UI programmatically?
How to Learn what Auto Layout Errors Mean
You’ve done the Stanford iOS course and all of the Wenderlich Auto Layout tutorials, but your app is still dumping
Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want
to the console.
How to Dump the Storyboard but Keep the Visualization
Storyboards get a bad rap. Sure, they are impossible to test and code review, and merges are a real pain. But it takes a second to look at a Storyboard and visualize what the UI is going to look like (or even if you are in the right file). If only there was a way to preserve the visualization but dump the XML.
How do you keep Storyboards from causing merge problems later?
There’s this myth in the iOS community that “professional” iOS developers never use Interface Builder. It’s meant to imply that coding your interfaces is always better, and if you don’t do it, you are somehow less of a programmer. The myth perpetuates the idea that IB is a crutch, a toy, something that only newbies use.
I call BS.