Profiling memory allocations in a iOS project is probably one of my favorite things to do when building a project besides coding. Profiling gives you a sense of validation about how you have technically designed certain aspects of a project and it also gives you a sense of where you may have gone wrong and inadvertently created retain cycles, memory leaks, or zombies.
In my most recent adventures in iOS I had a string hashing problem that led me down the road of creating a machine learning algorithm in order to find the correct random hash string I was looking for. Looking back at the solution now, I was able to solve my problem successfully, but the solution I came up with to solve this problem is quite unsettling due to the variable results in time complexity derived from my solution.
I have always been on the lookout for a tool that I can use to synchronize files between two Rackspace Cloud Containers. I have looked high and low for a suitable tool that syncs files from an origin container to a destination container whether that destination container exists or not. Finally, I decided that if I want something like this then I was just going to have to roll up my sleeves and create the tool myself.
One of the major parts of any software development cycle is testing. Whether that testing is performed on just one feature or an entire product I think that any developer can agree that code and product functionality needs to be tested before it is deployed. As a developer, one thing that I continuously find myself wondering is when is it an appropriate time to test my code? I wonder if it cost effective and productive to perform testing on a feature by feature basis? I wonder if I should wait until an entire section of features is completed to test functionality?