Goodbye Things, it’s time for a new focus: Omnifocus

Since my reset earlier this year I have been finding new ways to improve my productivity. One of these ways is tracking and managing my todos. Although previously an avid user of Things, the task management app which I have used for the last few years, I have been very insistent on switching applications because of the company’s slow iteration and improvements.

I had searched out many applications (Wunderlist, Trello, Reminders, Todoist) for the last 6-8 months and even tried and liked Omnifocus’s two week trial. However, after those two weeks, I was reluctant to pull the switch for two reasons:

  1. Cost. While it is difficult to put a price on productivity, shoveling out $140 for a set of applications which you cannot even try on iOS devices is a commitment.
  2. Change. Switching methods of productivity can prove daunting. Hell, changes in anything of ones life can be challenging; however, if that change can bring overall improvements, then change is good.

Thankfully, XWP recently gave out a technology allowance for us and I decided to use this to change my todo management application and switched fully to Omnifocus.

Now, after using Omnifocus for a few weeks, I regret not switching sooner. By comparison, Omnifocus is worlds ahead of Things. Even ignoring the UI, Omnifocus provides a much richer experiences for adding, organizing and managing todos.

If you are using Things, and irritated by the slow iteration and lack of features, I highly recommend switching to Omnifocus.


Make Mistakes.
Fall down.
Get back up.
Dust yourself off.
Find new beginnings.
Do not worry.
Keep moving forward.

This came to me today out of the blue and really touched my heart. When I read this, I think about my grandfather and the hardships he has been through, things he has learned and passed on to me. I am grateful to have such an amazing father figure in my life, especially right now.

Should we use snake_case in WordPress JavaScript?

Let’s start a discussion about WordPress JavaScript coding standards.

This is an age-old discussion that extends way beyond the realms of both WordPress and JavaScript, but I have always been a fan of snake_case over CamelCase. There is no refute that in regards to legibility, snake_case takes the cake. No matter how you slice it.

The current WordPress standard for PHP is snake_case, yet the standard for JavaScript is CamelCase. While this may not be an issue for most full-stack WordPress developers, developers that are usually focused on one language may have a tedious time remembering to change their coding habits completely in order to write a different the other. Which will cause inconsistency.

Besides, would it not be much more efficient to have one naming convention for all sets of code on the project?

I have always preferred snake_case and push everyone I know to write JS in snake_case; however, it is not so easy to change a standard (for good reason).

So please, take this short poll and let’s see where we stand.

First ride through the city of Seoul

Today I went on my first ride through the city of Seoul. Not along the river or on the bike trails, but through the busy streets, directly in heart of the city. Weaving around vehicles and traveling just as fast as the cars on the road.


This was the most freeing experience ever while riding and I now understand why bike messengers risk their lives everyday in New York (and other large cities).

I have never been fearful of riding through the city, but have not done it yet because I continually listened to others around me telling me I should not, because of the danger.

Today, I chose not to listen any more.

Yes, it is very dangerous. So is skydiving, scuba diving and even driving. However, we cannot stop ourselves from trying an experience simply because of the danger (or what others say).

Today was one of the best rides of my life and I look forward to many more. The others will just have to deal with their own fear.

Also, I made a quick stop to my favorite salsa club in Seoul and took a break under the bridge.