Software Engineering in WordPress, PHP, and Backend Development
When it comes to turning a profit on open-source software, I’d like to think that the majority of developers follow the same set of ethics. I’m my experience, it’s true – though, as with anything, there are outliers.
As I continue to work to introduce a premium level of support for my WordPress-related work, one of the things that I’ve found myself wrestling with is turning a profit on work to which others have contributed.
But are open source ethics that complicated?
The past couple of weeks, I’ve been discussing the challenge of supporting free WordPress plugins. Though I’ve done this in the past, I’ve retired those projects, but am looking to get back into doing so all the while documenting the process here.
But first, for those who haven’t been reading the articles up to this point, I wanted to reference the previous posts just to let you know where I stand with regard to all of this:
The point is that I’m slowly working my way back into building a small business around building WordPress plugins, supporting them, offering documentation, manuals, and so on, but I want to make sure that I’m doing it right.
To that end, I’m enjoying the discussion with you guys via the comments as well as the challenge of finding the best tools possible not only for me but for potential customers, as well and this is what raises my next issue: Finding the right WordPress support system. Continue reading
One of the biggest problems with writing and maintaining themes and/or plugins in WordPress is the frustration that comes with having to track down JavaScript errors.
Pippin Williamson has discussed this extensively on his blog, we’ve covered it on WP Daily, and I’ve talked about this once before here.
But since I’ve seen this issue crop up several times since, I wanted to offer some additional thoughts on this particular topic that has stemmed from the recent discussions.
Last week, the Everyone Should Learn To Code video was making the rounds around the web. If you’ve haven’t seen it, I’ve shared it below.
In short, the video opens with a quote by Steve Jobs:
I think everybody in this country should learn how to program a computer because it teaches you how to think.
In short, it’s an inspiring video that features some of the most popular technologists discussing their thoughts on programming, their foray into the industry, why others should follow suit.
This idea isn’t new, but the popular nature of this video has really gotten me thinking about my particular stance on this issue. In fact, I read a strong rebuttle to the video last week that – whether or not you agree with it – is a well-written piece.
I shared my candid thoughts with my team on our back channel which resulted in a bit of a discussion primarily between John and myself. The more I’ve thought about it, the more of an opinion I’ve developed, and thought I’d share it here.
TL;DR: I’m not completely sold on the fact that everyone should learn to code. First, I think we need to define what it actually means to code.
As previously mentioned, WordCamp Atlanta 2013 will take place on March 15 – 16 at The Loudermilk Center. I’ll be speaking on Saturday, March 16th at 9:00am for the Developer Track.
Specifically, I’ll be speaking on how to Level-Up Your WordPress Development Skills.
Generally speaking, I’ll be looking to speak to both beginner and intermediate WordPress developers, but hopefully providing some useful information for advanced developers, as well.
That said, I thought it may be worth looking at a few of the topics I’m planning to cover during the course of the talk:
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.
© 2026 Tom McFarlin
Theme by Anders Noren — Up ↑
