Tom McFarlin

Software Engineering in Web Development, Backend Services, and More

Page 231 of 433

Two Take Aways From Jason Schuller’s Pickle Project

Earlier this week, WP Tavern wrote up an excellent piece on Jason Schuller’s newest project, Pickle

I’ve ended reading over the article (and the comments) a number of times because I think there are some really, really great though as it relates to using WordPress as an application platform.

 Jason Schuller’s Pickle Theme Re-Imagines WordPress as an Invisible CMS

This is something that I’ve talked about a number of times and it’s something that I really want to see happen more and more in the future; however, this is one of the first times that I’ve really seen someone take WordPress, use it as a foundation for solution that’s built towards a specific market, and then articulated it in such a way that does a great job of expressing what exactly it means for WordPress to be an application platform.

Continue reading

Using Transients For Storing Google Maps Data

A couple of weeks ago, I shared a quick tip on working with multiple InfoWindows with the Google Maps API specifically within the context of WordPress.

Google Maps InfoWindow

When working with this API, there are a number of considerations to take into account each of which is going to depend on how much of the API you’re going to be using; however, one constant that’s going to remain regardless of how much you’re using is the rate limit.

That is, unless you’ve paid Google a decent chunk of change, then you’re going to have to take rate limiting into account whenever you’re working with this API. And if you’re charting quite a few locations for, say, several different pages or several searches, then you can hit that limit quickly.

If you’re not at the point where you can pay Google to up the rate limit, but you’d like to still make sure your project doesn’t totally bomb out if the rate limit is hit, then I recommend using transients to store Google Maps data for an interval of time so that you aren’t making frequent calls to the API.
Continue reading

The More Things Change, The More They Stay The Same

Generally speaking, people often set out to try to set their plans, goals, and resolutions at the beginning of the year. I did though it’s not really something I typically do, and here we are at the beginning of March and I’ve really only done a portion of what I thought I was going to be doing.

I mean, I haven’t even touched Swift yet (and I don’t know if I will end up doing so).

Then again, Pressware has been growing and has resulted in the need for me to make some changes both to what I’m doing with some of my open source plugins and with what I’m planning to do with the business itself.

It’s both an exciting time, but it’s also a really weird time because it’s causing me to evaluate some changes that I’m making in a number of things that I’ve been working on for several years at this point.

When this happens, I can’t help but feel a little bit of tension – maybe even some fear – of letting certain things go. On top of that, I think that it can also breed a sense of relief as it may bring about a little bit of breathing room.

But does it really? I mean, when we wind down work on one thing, are we just making space to spin up something new?

For me personally, what I’m finding out – and it’s sort of a cliche – is that the more things change, the more they stay the same.

Though I may be winding down certain things, other things are starting up.

Continue reading

Aesop Story Engine and WordPress (Why Do We Reject Our Own Innovation?)

For some time now, I’ve been a big fan of using WordPress for web application development, but I think that developers actually embracing the CMS (let alone seeing the CMS) as a foundation for something like that is still a couple of years off.

Sure, we’re going to see some people using it for things like that. I mean, we’re already seeing some out-of-the-box applications like AppPresser, but projects like that are the exceptio, not the rule. In my own experience, I’ve found that clients are very interested in using WordPress, but using it for more application-like capabilities.

This doesn’t mean that gigs for themes, plugins, and what not are slowing down, but that people are wanting web applications for themselves or their companies, but want to be able to administer it using the WordPress dashboard or using a some custom front-end work.

But that’s beside the point.

What I’m getting at is that as developers, designers, and other people end up seeing WordPress as potential foundation for web application development, the more innovative things we’re going to see entering the space.

Continue reading

« Older posts Newer posts »

© 2026 Tom McFarlin

Theme by Anders NorenUp ↑