Author: Tom (Page 242 of 428)

The WordPress Post Editor Doesn’t Suck (Though We Might Be Lazy)

November 12, 2014 / Tom / 0 Comments

There was a great article written on WP Tavern yesterday entitled Why WordPress Doesn’t Need To Fear Ghost, Yet.

And before I go any further, I want to be absolutely clear that as much as I know that people who are involved in WorPress love a good dramatic story – especially one that involves mudslinging and controversial statements that generate all kinds of fun conversations in comments and on Twitter – this is not one of those stories.

Don’t read it that way, don’t spin it that way, and don’t try to twist any of the words that are in here as that’s that the purpose of what I’m trying to say.

Instead, this is my take on two of specific topics that were discussed in the article.

My Suite of Apps: Safari

November 11, 2014 / Tom / 0 Comments

I know – Chrome is arguably the best web browser (or at least the most popular) on the market right now. Ever since the first version was released, I used it religiously (and I used Firebug and Firefox when I needed developer tools until Chrome’s finally shipped).

But when the latest version of OS X shipped, I decided to give Safari a try if for no other reason to see if the claims about its speeds were true, and to take advantage of Continuity.

Like any other web developer, I still have other browsers sitting on my machine so that I can use them for testing and so on, but I’ve actually been using nothing but Safari since Yosemite’s launch and I haven’t missed my other browsers.

In fact, I’ve enjoyed using Safari more than any other browser because of its integration with other devices.

My Suite of Apps

November 11, 2014 / Tom

Over the last few years, the categories and tags on this blog have renamed consistent. That is, the categories with which I started out with haven’t been changed, removed, or have seen any additions since I’ve been running this blog.

Generally speaking, I say that’s pretty good – it means that all of the content that I’ve wanted to share has fit within the categories that I originally planned. As such, when I set out to write about the things that, y’know, originally wanted to write about, I had defined the focus of the content and have done relatively well at keeping content consistent within those categories.

Today, I’m going to be adding a new category to the blog (I know, I know – call down, right?) in order to support some upcoming articles that I’ve been planning to write but never really had the desire, need, or want to do so.

Using GitHub Issue Checkboxes

November 10, 2014 / Tom / 0 Comments

One of the things that I like most about working with issues in the context of GitHub is that you can classify them based on what type of issue. That is, they can be be bugs, enhancements, features, or any other custom label that you opt to display them.

On top of that, GitHub-flavored markdown also makes it easy to to write well-formatted issues and comments on these issues. Over the course of this year, one of the things that I’ve found myself using more and more when filing issues has been using checkboxes to help break issues down into more incremental steps.

Your Decisions Are Weak (Throw The Baby Out With The Bath Water)

November 7, 2014 / Tom / 0 Comments

It seems to be relatively common in the online developer community to easily dismiss others’ work when it doesn’t align with whatever we consider to be the best way to go about doing something.

I think it’s fair to say that this is something that we’ve all seen, too: Think about one of your favorite libraries, frameworks, applications, dependencies, or whatever, and then think about how critical and dismissive other people – or even ourselves – can be of the work.

Honestly, there’s nothing wrong with being critical – I think it’s helpful because it forces us to justify the decisions that we’ve made, defend our rationale, or even rethink our approach.

But when it comes to dismissing something solely because you dislike how it’s done represents a ill-formed perspective on the work that someone has done and a lack of understanding as to why things are the way they are.