I want to share a couple of exceptional software programming talks that I've watched recently. They are both engaging, and if you're anything like me, will likely challenge many of your assumptions while enforcing other suspicions about the "right" way to write software.
You'd think something as simple as an automatically incrementing build number would be a solved problem by now. Instead it seems to be one of those areas where everyone has their own workaround. At least for those of us not blessed, or cursed, with a monolithic shared build system. For Cocoa apps the build number is also known as a `CFBundleVersion` and it's a very useful thing for lining up bug reports with exact points in your code history.
Functions are first-class citizens in Swift. They can be stored in a variable or constant, passed to another function as a parameter, or returned as the result of another function. This concept of "functions as data" enables the development of complex systems composed of small bits of reusable logic in an elegant and concise way.
If you're trying to use the Google Place Search API with an iOS public API key and you get the error message, "This IP, site or mobile application is not authorized to use this API key.", this might help.
Swift properties aren't sacred.
Swift beta 5 introduces some new rules that effect view controller subclasses and initializers.
Posting to Notification Center center from a shell script is a great way to let yourself know that a potentially long process has completed. Luckily, it takes just one line.
Jabra could be working on a new version, getting out of the headphone market entirely or retailers are just clearing out excess stock. Whatever the reason, it's a buyers market for these Bluetooth headphones.
Getting a clean install of OS X 10.10 Yosemite is possible, if not straightforward.
WWDC starts tomorrow and from what I've heard it's going to be a big one. Unfortunately, I didn't get a ticket this year so I'll be following along from home.