Software Engineering in WordPress, PHP, and Backend Development

Author: Tom (Page 339 of 427)

Category Sticky Post 1.2

Last week, I release a relatively major update to Category Sticky Post. For those of you who have been reading this blog for some time, you know that I released the first version back in August of last year.

Since then, there are been several minor updates most of which were primary bug fixes or hot fixes.

Though this update is still a relatively minor update, it introduces a few things both behind-the-scenes and functionality-wise that should improve how it works especially with posts having multiple categories

Continue reading

SysInfo For WordPress System Info

One of the neat things about attending conferences like WordCamp Atlanta is that you get the opportunity to get some facetime with other people that you may typically only interact with via Twitter.

Case in point: This past WordCamp Atlanta, I had the pleasure of hanging out with Dougal Campbell, Brian Krogsgard, Dave Donaldson, Mike SchinkelJonathan DavisJames Dalman, and others.

But one of the neater things that happened was, over lunch, Dave happened to demo something that he had baked into a number of his Max Foundry products. Specifically, it was a WordPress system info tool specifically for helping him diagnose errors while handling support requests.

During a brief conversation, he mentioned that he was considering releasing it as its own plugin and placing it on GitHub.

I dug the idea.

Continue reading

My Preferred Web Page Screenshot Tool

I try to keep a running list of the tools that I use in my day-to-day development. The challenge in doing this is that finding new tools can get buried in that single post, so whenever I stumble across something that I introduce into my toolbox, I try to capture it here.

Other examples include:

With Chrome being my preferred browser, I’ve had a hard time finding an extension for taking a web page screenshot that I really like – every single one of them as come up short in one way or another.

Except for this one. Continue reading

Software Craftsmanship and WordPress

Earlier this year, I shared a post on why software craftsmanship matters in WordPress development. It stemmed from a Twitter conversation that I had with Dave Donaldson at Max Foundry.

In the comments of that particular post, Dave also followed up with this comment:

Just to be clear, my issue with the term “software craftsman” is that it’s taken on an elitist connotation by many people, and that bothers me. It also bothers me that there is some correlation between people who spout “software craftsmanship” but don’t actually ship anything.

I try not to spin my wheels on topics that I’ve already discussed in-depth, but I recently stumbled across another post by Uncle Bob Martin – arguably the biggest proponent of the software craftsmanship movement – on the 8th Light blog that brought up the same concerns that Dave mention.

Specifically, it discussed the “elitist connotation [demonstrated] by many people.” Call me naive but I’ve simply been missing out on the drama that’s been going on surrounding this entire “software craftsman” thing.

For me, it’s always been about the manifesto, and the ability to make sure that I – as a developer – am doing the best job that I can to build good things for others and for myself.

It’s also a matter of making sure that I’m actively trying to learn from others as well as evangelizing my own practices to others not because I think that I’ve got it figured out, but simply to give back to the developer community.

But apparently, there’s more going on.

Continue reading

How To Document WordPress Projects

Earlier this week, I wrote about the challenges of documenting WordPress projects regardless of if they are free or premium.

In the post, I mentioned that another challenge that comes with actually documenting a project is making sure that you’re catering to the various ways that people learn.

First, as a general rule, I think that projects should include:

  • Source Code Documentation. Free projects should have code comments, premium projects should have code comments, PHPDoc (or similar) style documentation, and API documentation if one is available.
  • A Manual. Free projects should have a README and potentially a web page, premium projets should have a manual that’s perhaps its own website complete with screenshots and/or videos.

But this raises a second question about WordPress documentation, specifically around premium projects: If people have different styles of learning, that is, some learn better by reading, others better by watching, are we obligated to provide both forms of documentation?

Continue reading

« Older posts Newer posts »

© 2025 Tom McFarlin

Theme by Anders NorenUp ↑