Software Engineering in Web Development, Backend Services, and More

Author: Tom (Page 221 of 433)

Things That I Believe Every Project Needs

When working on software development projects, there are certain things that I think every project needs. Sure, each project is different so there’s definitely a difference among projects, but in my experience there are a few things that are crucial to both managing a project and completing a project.

Honestly, when it comes to writing posts like these, I think our natural tendency is to do so from the perspective of a freelancer or someone who may be subcontracted or self-employed.

Though I tend to fit in the latter camp, I’ve found that the following tends to be true regardless of where you work – be it a big corporation, a small team, or even on your own.

Continue reading

Resources For The WordPress Theme Customizer

With the recent change to WordPress.org requiring themes to use the WordPress Theme Customizer in their work, WordPress designers and developers have been talking about it and discussing it for several weeks now.

And rightly so: Many of us are fans of the customizer, many are not, some fall in between, and some wish that there was a compromise.

As far as I’m concerned, that’s fine (though maybe I’m biased because I tend to be a fan of the Customizer), but whatever the case, this doesn’t change the fact that there’s a lot of education that needs to happen around how to use the API – which isn’t terribly difficult (in comparison, to say, the Settings API) – and how to make the transition over to it.

Continue reading

Quick Tip: Disable Scroll Zoom in Google Maps

One of the APIs that I find myself working with more and more for a variety of projects is the Google Maps API. Specifically, the Google Maps JavaScript API.

The Google Maps JavaScript API

Though we can do some really cool stuff with it, it’s not my favorite API to work with. Perhaps I’m missing something, but I don’t find it particularly intuitive and it takes me longer to read through the documentation to figure out how to do something that seems as if it should be simple in comparison to some other languages’ documentation.

Continue reading

Should We Share Old Code?

There have been times where I’ve considered pulling code down from the WordPress plugin repository or from GitHub because the way in which I write my code now differs from how I wrote my code when I was working on those projects.

GitHub Profile

And surely you know what I’m talking about: It’s not that the plugins don’t work and it’s not that they necessarily cause problems for anyone, but the open source nature of what they don’t necessarily represent what we’re capable of doing now or how we’re capable of doing it now.

Does that make sense?

Continue reading

In Development, Always Be Learning

Earlier this week, I wrote a post about how we use the term “WordPress Admin,” how I suspect that we’re using it incorrectly, and I discussed the significance and importance of consistency of terminology when working with customers and clients.

The post generated far more discussion than I would have expected, which is a good thing, but one particular comment struck a chord with me:

Tom,

I sent a Jr. level WP developer through your TutsPlus course on plugin development. You use the word “Admin” more times than I could count! You even use it for file names, etc.

What’s up with that, brother? I respect you so I had to chime in with that lil’ observation.

I love comments like this because not only does it hold us accountable to our own actions, but it also gives us an opportunity to show that throughout the course of whatever it is that we’re doing now may not what we’re doing tomorrow.

Continue reading

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑