Software Engineering in WordPress, PHP, and Backend Development

Category: Articles (Page 150 of 258)

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

Developer Fitness: Getting Back To and Staying in Shape

One of the things that seems to be unique to open source is many opt to share their annual reports of their business regardless of how the business performed over the year. Others also talk a lot about their mental health – again, regardless of if it’s good or bad. And when you’re part of a larger group of people who are doing the same thing, it’s really inspiring, educational, and also prompts you to aim to be a better friend and peer. An amiable goal by any measure.

In short, it’s something that’s really cool to see even if you opt not to disclose that information yourself.

However, one thing that we don’t see as much of – not because people don’t share it, but because it doesn’t seem to be as popular to share – is the idea of developer fitness. I know people are involved in all kind of things offline. For example, I know Sean Davis hosts a number of workout contests and is also involved in a number of different sports (most recently, racquetball based on his Twitter feed). I also know that Sunny Ratilal shares his FitBit progress throughout the week giving insight into his level of activity.

Cool, right?

Anyway, the point is that I know we’re all active in different ways but we don’t blog about it as much for whatever reason. And I get it: Talking about health, fitness, and exercising is boring. Or it can be boring.  It can also be a lot of fun depending on if you’re found the right kind of workout for you (more on this later).

Continue reading

Hey Programmer: Don’t Be a Jerk

Cliff, a local developer friend, happened to share this on Twitter earlier this year. I’ve been sitting on this post until I found a good time to post it.

Of course, I don’t know what a “good time” is, but since I’ve had this drafted and I’m on the road right now, this seemed like as good a time as any.

Anyway, I thought that it was something that we could all read, learn from, and carry forward in our day-to-day interaction online.

Continue reading

WordPress and Theme-Specific Plugins

When it comes to working with WordPress themes and plugins, there’s a general rule of thumb that most experienced designers and developers follow:

Themes are for presentation, plugins are for functionality.

Sure, there’s a little bit of blurring of lines, but this is the goal for which we strive when working through our code. And yes, there’s a lot that can be said (and has been said) about themes that include a ton of features, options, bundled plugins, and so on, but that’s not where this is going.

WordPress Themes

Instead, I’ve been thinking about how this relates to general theme development, niche theme development, and using WordPress as a platform for application development.

Continue reading

Two Tips for Writing WordPress Plugins

Occasionally, I’m asked for two quick tips or suggestions that I have for those who are just getting started with writing WordPress plugins.

WordPress Plugins

The assumption is that they’ve done all of the necessary leg work to get to the point where they are comfortable writing code and working with WordPress, but they want to avoid some of the pitfalls that many (or most?) of us experience when we first get started on our own projects.

Continue reading

TinyMCE and WordPress: Adding User Input

In the previous post in this series, I showed how to add content to the post editor using a custom TinyMCE button. The problem with the approach, as we’ve covered thus far, is that the content that we’re adding to the editor is hard-coded.

We’re rarely going to want to be doing this, right? I mean, wouldn’t we rather grab input from the user and then add that to the editor?

My very own copy TinyMCE Editor. Show spectacular.

My very own copy TinyMCE Editor. So spectacular.

For some, this may be creating a shortcode based on some input, for others it may be grabbing input, making an Ajax call, and then putting the result of the request into the editor, or it may be something as simple as taking whatever input the user has provided in a prompt and then adding it to the editor.

Though the latter case is not likely something that is a realistic use case (after all, if they just wanted to put something into the editor, why not just, you know, enter it into the editor?), it’s something that will make rounding out this series a bit more complete because it will show how to connect displaying a prompt to the user, grabbing the input, then using the TinyMCE API to drop the input into the editor.

So that’s what we’ll do.

Continue reading

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑