This week I heard some chatter in certain iOS groups that I belong to about whether testing your iOS, macOS, watchOS, or tvOS applications provided any immediate value in the development life cycle. As opposed to developing features without testing and getting them to market right away and then iterating upon them in a highly agile methodology. Coming from a background where I like to write a lot of automated tests and system tests for software that I write, I have to admit, this point of view really made me pause for a moment to try and see the perspective from both sides.
Today I was analyzing a potential bottleneck in some computation I was doing with Swift and thought I would try a basic linked list data structure to store data instead of an array. It soon dawned on me that I have never created a linked list in Swift before and thought this might be a good opportunity for a Swift Playground to test out my idea. Sure enough, using Playgrounds was a great way to test out my code and make sure it was running the way I wanted it to before integrating it into my project.
Last week I started building an iOS application in Swift 3.0 and Xcode 8 and was able to get a good portion of the application completed. Towards the end of last week I became aware of the need to integrate a Unity / Vuforia exported project into my existing iOS Swift project to enable an augmented reality feature in the iOS application I was working on.
Yesterday I was catching up on some of the recent proposals on the Swift Evolution Github page and seen a very interesting proposal that I thought I would discuss in brief detail.
This past weekend I am happy to have attended PyData Chicago 2016, put on by PyData and held at the University of Illinois Chicago at the UIC Student Center. PyData Chicago 2016 was a conference all about using Python along with data science and open source tools to help data scientists, developers, and academics better get their jobs done in a more efficient way. Before I go any further...