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.

Hitting the Reset Button

There you are, sitting in your chair and happily playing Legend of Zelda: Ocarina of Time. You just reached Ganon with the will of an entire army to defeat him and save Princess Zelda. All of a sudden the screen freezes. You hope that this glitch will just go away, but unlike the buffering of today, this freeze with not fix itself.

You know what you must do. You have to hit reset.

This is what I am doing with my person site. Hitting reset.

Over the years I have published many posts, many I am proud of and some not so much (hindsight, am I right?). Now, I want to refocus my writing on my blog to reflect more about myself, my thought and my beliefs (something my old blog did not do).

So, what’s new? Well, I am now blogging on instead of using my own personal blog. My personal site has always been my online home and over the years, I have recognized that I always wanted to rearrange the look, tweak the performance, or simply play around with the code. While doing this, I lost focus on the content.

In the long run, will save me time and money (see Phillip’s post for more information and my inspiration).

So, what about the old content?

That is a good question and I simply do not have a definite answer just yet.

I do have plans to move many posts, pages and projects over. Some of the other content is very outdated. These may not be moved over, but archive locally instead (for my future reference). In addition, many items are marked as tutorials and these will most likely be moved over to my Gist account.

Moving forward, this blog will transition from a jumbled mess of this and that to a more focused blog about me, my life, my thoughts and my beliefs (as mentioned above).

Looking forward to my next post!