Software Engineering in Web Development, Backend Services, and More

Search: “wp_query” (Page 26 of 29)

We found 145 results for your search.

An Embarrassing First Release

I’ve talked before about my idea of shipping a “strong 1.0” when it comes to working on projects for yourself or for other people but what if that version is an embarrassing first release?

There’s a quote that many of us are familiar with (and that I’ve referenced here before, too):

> If you are not embarrassed by the first version of your product, then you’ve launched too late.

It’s attributed to Reid Hoffman, the founder of LinkedIn.

I think it’s something that’s good to remember, but sometimes I wonder if we use it as a crutch when shipping something and as a rationalization to cut corners.

Highlight a WordPress Admin Active Submenu

If you’re working on a theme or a plugin for WordPress and you want to highlight an active submenu item, then your implementation is going to vary based on where you want to highlight the actual item.

This is one of those times where it’s helpful to have clear terminology for what you’re trying to modify:

– Are you working on trying to highlight an active submenu in the admin menu,
– Or are you working to highlight an active submenu on the front-end of the theme?

There’s no consistent way to do this. For what it’s worth, I don’t think they should be as they are two completely different entities (for lack of a better term). Perhaps having some semi-consistent filter names would be nice, but that’s about it.

Regardless, when you set out to highlight an active submenu item, it’s important to note which part of the project you’re working on and then go from there.

The Tension of Refactoring Legacy Code, Part 2

In the previous post on refactoring legacy code, I talked a bit about the challenges that we face not only as WordPress developers but as programmers in general as it relates to working with legacy code.

The short of it is that I believe we want to make sure the codebase is as optimized, clean, and well-organized as possible. But the reality of a project prevents us from doing this.

Perhaps it comes in the form of the team we’re on; perhaps it comes from deadlines that are looming, or perhaps it comes from something else.

Whatever the case, we’ve established that a tension exists. And though I’ve talked about some general ideas as to how to deal with it, I haven’t really talked about my own experience in doing so.

The Modern WordPress Server Stack

During WordCamp San Diego, I had the pleasure of meeting and hearing Carl Alexander speak on the topic of the modern WordPress Server Stack.

A few notes:

– If you’re not following Carl on Twitter, I recommend it. He’s an incredibly smart person who is doing some really neat things with WordPress (such as TwigPress).
– If you’re not subscribed to his blog but are interested in advanced programming topics as it relates to WordPress, I recommend subscribing.
– If you weren’t present for his talk, you can catch it on WordPress.tv.

With that said, Carl also included an article that accompanied his presentation on his blog and it’s something that I think makes for good reading.

I find this especially true if you’re someone who is at an intermediate level of WordPress development or if you’re someone who’s looking to learn more about server administration.

Scaling WordPress (And Doing It Right)

Scaling WordPress is a hot topic among developers.

For some, it’s just something you do through a variety of tools and practices that you learn over time. For others who are involved with development in other languages, it’s a fool’s errand.

As far as I’m concerned, WordPress does scale though it takes some strategies to get it to work (such as a proper use of transients, caching, etc.). But there are varying degrees of what it means “to scale,” right?

That is, depending on how many users you have, the type of content you’re serving, the level of demand your site has based on the interaction of the visitors, and some other factors will all contribute to whether or not your site is going to scale.

But if we’re working on a larger project and we know it’s going to need to scale, how do we know we’re doing everything correctly?

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑