Software Engineering in Web Development, Backend Services, and More

Category: Articles (Page 176 of 259)

Personal opinions and how-to’s that I’ve written both here and as contributions to other blogs.

Don’t Be Afraid To Ask For Help

This weekend, a fellow tweep and developer shot me a short question that I think hits home for anyone who’s involved in development regardless of skill level:

Question for you, do you find it hard to ask for help when you get stuck on some code?

Perhaps I should’ve just easily said “Don’t be afraid to ask for help!” but my short, 140-character-or-less answer was:

no. early in my career i did, but not anymore.

But this is one of those things that’s so common for many of us and since Twitter greatly limits just how much we can say (which is a good thing, in some cases), I thought it worth talking a little bit more in-depth about it

Continue reading

Premium or Commercial Themes (Which is it?)

One of the discussions that I’ve seen crop up more than once is the debate as to which should those themes for which we pay be called Premium Themes or Commercial Themes.

Though I personally call them Premium Themes, there have been times in which I’ve casually referred to something as a Commercial Theme. And this is something that we could all debate ad nauseum and probably still not come up with a definitive answer, so I realize the potential futility of writing a post like this, but my curiousity is piqued:

What is the best term to use when talking about themes that much be purchased?

For me, it’s a matter of looking at the basic definitions.

Continue reading

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

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.

WP Tavern

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.

Continue reading

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

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.

Continue reading

A WordPress Theme Development Process

Although I still stand by the idea that we all have the ability to decide how complex or how simple we create our themes, I do think that there’s something to be said for identifying the core problem a given theme is trying to solve.

That is to say, is a given theme trying to:

  • Target landing pages for a certain type of niche business?
  • Create a reading experience that looks ideal on mobile devices?
  • Serve as a tumblr-esque type of blog?
  • Meant to serve as an online journal for, say, photos or music or videos or something similar?
  • …and so on

In short, I think that when someone asks you “what does your theme do?” or “who is your theme for?” then you should be able to quickly give an answer. Saying something like “this theme is for the small business owner who runs a restaurant, or a body shop, or a photography studio, or a convenience store” is too broad.

If we use personas as a way to identify who our themes are for, and a persona represents an actual type of person, then doesn’t it seem highly unlikely that a person who runs a restaurant may also be the type of person who is a mechanic and/or a photographer?

What I’m trying to say is that whenever we sit down to begin planning out and building our themes, I think that we need to do a better job of identifying both who the theme is for the and what the problem space is that we’re attempting to enter.

Some personas should be taken more seriously than others, I think.

Some personas should be taken more seriously than others, I think.

Of course, this isn’t to say that some teams don’t already do this. In fact, I can think of quite a few who do and who do it really well. Other times, though, I think that many try to create themes more or less to show off what they can do with WordPress rather than to truly serve a need that a potential set of customers may have.

So where do this leave us? That is, how can we do a better job of approaching theme development in such a way that’s it’s solving problems and catering to a certain type of customers rather than just trying to be the next flashy product that offers n-number of a features and m-number of options?

Continue reading

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑