Code organization is a matter of hygiene

Having a clean, organized code means that anyone can easily maintain it. There will be no hassles when trying to read and understand it. Being able to rapidly find a method based on it’s scope is a gift. So I thought I’d show you my way of organizing properties and methods within a class.

Recently we had to integrate a chat-like comment feature to our new Winnin App Our backend team decided to build it using websockets, so when it came to the app implementation, my first thought was to search for an opensource swift framework that did confirm to the Websocket Protocol. We decided to go with Starscream since it seemed simple and reliable enough.

These days I had to convert the core of an iOS app to a framework that could be shared between projects. It was fairly simple considering the “new” framework products available in Xcode. I managed to build it with the desired public headers, copied it from the “Products” folder to the new project and everything flowed smoothly.

Finally! After long overdue, this lovely little blog has been updated. And upgraded. From one press to another. So long Wordpress, hello Octopress! And we’re now hosted on Github. So, if I ever get lucky and have a truly successful post, there’s no need to worry with the blog being down.

Have you ever used git-blame to blame on people? I have and I was wrong more often than I was right. When I wasn’t the one blaming others, the fingers almost always pointed at me when something went wrong. The problem with “default” git-blame and Xcode’s blame view is that it only shows the last person that committed the lines in question and, not necessarily, wrote them.