TL;DR: As much as I like using object-oriented programming for writing code, it’s not the only way to write code. The same goes for WordPress-centric code, too. When writing solutions for WordPress, don’t set out to write everything in an object-oriented way. Don’t forget procedural programming in WordPress.
For the last few months, I’ve been writing a handful of small utility plugins (for lack of a better word) for WordPress. These are things that are designed to do at least one of the following:
add a feature that I wish exists but doesn’t,
improve functionality of the administration area to make achieving a given task easier,
introduce functionality that’s easier for a sites that have a large database of users,
As someone who’s historically been one to go on and on about why we should be using object-oriented programming, I’ve not been doing much of that in these plugins.
Instead, I’ve been using some features of PHP, like namespaces and autoloading, to keep the code running in its own area to prevent potential conflicts with other plugins. I’ve also been using PSR12 with procedural programming.
For as much as I’ve written about object-oriented programming, I don’t think I’ve written enough (and I certainly won’t do so in a single post 🙂) about procedural programming.
But that doesn’t mean now isn’t as good as time as any.
TL;DR: This is everything that needs to be done to install Xdebug with a Homebrew-based environment and to work with the software within Visual Studio Code.
Though I’ve recently become a fan of using Ray (1, 2) for much of my lightweight debugging, this doesn’t mean I don’t think it’s important to have Xdebug installed and configured in Visual Studio Code.
If you follow the steps I’ve outlined starting in the previous post, it’s relatively easy though it still requires a little bit of manual work to get started.
This is how you can set up Xdebug with a Homebrew-based configuration and Visual Studio Code.
I have different tools for productivity as well as for personal use.
And how I set all of this up has changed, too.
Since it’s been about four years since I’ve written anything like this, now’s a good time to document my current set up both for reference and to share with the rest of you who find this kind of stuff interesting.
I’m not, nor rarely have been, much of a procrastinator. If there’s something that needs to be done, I try to take care of it in a timely fashion. Sometimes it’s easier than others, but on the whole I dislike putting things off.
To that end, I’ve used the methodology of Getting Things Done for years with the help of a couple of utilities, like Things, all of which are beyond the scope of this article.
You can read about the workflow in the article linked above. The purpose of mentioning it to show that even when I lean towards procrastination, I have a plan for how to tackle something.
To that point, there’s been book of which I’ve been aware for roughly three years that I’ve deliberate put off reading. Perhaps I’ve even avoided reading it for reasons that I’ll soon explain.
If you are looking for WordPress guides and unbiased reviews, I recommend checking out WPKube. They also have an exclusive deals section.
Just Getting Started with WordPress? I write a lot about WordPress development but if you're just getting started, I recommend checking out WPBeginner. They have free training videos, glossary, and more.