I recently took on the challenge of working on Sendible’s mobile application. I first started working with the android application written with Java but before I knew it there was a need for similar changes on the iOS application. I have had some experience with iOS but never released an app written in Swift, the last iOS app I was involved with building was written in C# (Xamarin). This post is part of a series that will document my journey towards becoming a proficient iOS developer.

Society tends to reward people for coming up with answers but often sees people that come up with questions as a distraction or difficulty, but yet every good answer requires a good question. What if we approached things differently, what if we not only rewarded the kid with the correct answer in class but also the kid that raises their hand with a good question.

I recently took a decision to publish daily because I believe that doing so will enable me to start small, fail small and eventually someday through compounding effect, what started small will eventually be big. The reason I mention this is because the commitment has made me realise I need a plan. As much as I consider myself agile and flexible, there are times when I just don’t have the words to say or write or don’t feel like delivering or releasing any of my work and during those times it helps to have a plan.

In this post I am going to touch on two values from the agile manifesto which in my opinion seem to be the most misinterpreted.

Like most people I tend to hesitate to publish anything to the public until the point I think my creations are perfect or at least good enough for public consumption. But sadly this way of thinking has limited me from seeing most projects I’ve started come to fruition. I believe I’ve found a better way and this is why.

At my current company (Columinate at the time of writing) we write code in Clojure and ClojureScript. I have often been asked the question “Why Clojure?”. I hope to answer this question with this blog post and to highlight some of the key reasons for choosing Clojure.