Pattern matching, the value of smaller blog posts and a new word

12 November 2017

Three things I learned this week were: pattern matching to turn noise into meaning, I published my first entry on my swift learning journey and I learned the word ‘liminal.’


My Swift Journey - The Basics

11 November 2017

I am currently learning Swift to expand my programming knowledge. I looked at Swift a few years ago, but am now ready to dive into it.


More on the async attribute, Swift progress and naxos music library

05 November 2017

This week was tough. I did not get much time to code as my time was consumed by chores and housework. This list is not great, but, it is what it is. So, the three things I learned this week were:


Formatting Jekyll HTML output, third party JavaScript and the async attribute

29 October 2017

Three things I learned this week were: styling HTML output with Jekyll, checking third party APIs and the async attribute.


3 things: Swift functions

22 October 2017

This week’s post is all about Swift functions.


3 things: Swift, CRISPR, WEIRD

15 October 2017

I’m trying something new. I’m going to record three things I learned or found interesting in the past week. I don’t think these will be long or in-depth posts. Just a quick note to myself about where my mindset was for the past week. I’ll see if I can make a habit of it or not.


Make An UIWebView Transparent

11 July 2017

I’ve been playing around with iOS. One challenge I came across was how to make a Web View transparent. I found two ways to do this: using the Interface Builder in Xcode or using Swift.


3 Things I learned from the Introduction to Mathematical Thinking class

10 June 2017

I took the Introduction to Mathematical Thinking class to improve my logical thinking. I found the class difficult, but I enjoyed it. The class covered many topics including truth tables, number theory and real analysis. The following are three things I learned that I can apply to programming or every day life.

1 - Understanding versus solving a problem

When faced with a problem it is natural to want to dive in and solve it. However, it is important stop and examine the problem. Is there a pattern? Does everyone have the same context for the problem? Is there ambiguity about the requirements?

Mathematical thinking focuses on understanding a problem rather than rushing to solve it. This is because finding the answer solves that one problem. But, understanding means the solution can be applied to many problems.

One example from the class was to find the double meaning in the following statement:


I'm taking a math class

16 January 2017

I’m starting 2017 by taking Coursera’s Introduction to Mathematical Thinking class. In my previous post I noted I should focus on programming projects. I realize I am distracting myself from that goal. However, I am taking this class for the following reasons:


2016 Reflections

31 December 2016

What I did in 2016:


  • I coded!
  • My python knowledge has improved.
  • I contributed a small amount to open source.
  • My command line skills have improved.


  • I did not have a focus. I split my time among coffee script (hubot), wordpress and python.
  • The time spent on hacker rank distracted me from doing another project.
  • Nothing gets done in December. It is all illness and family functions.

What I can do to improve in 2017:

  • Focus on projects. Come up with a plan on what I want to work on and stick to it.
  • Pick a language to focus on.

Happy New Year!