One of the more challenging aspects of working with WordPress is working the fragmented nature of documentation. And I don’t necessarily mean the Codex nor do I mean the Developer Resources.
But I mean the fact that there’s a ton of information spread across blogs (mine not exempt), subreddits, questions and answers on Stack Exchange, and shares via Twitter, and so on.
I’m not making a case that this is inherently bad or good but I am making the case that when given the opportunity to provide a central repository of information for a feature, set of APIs, or tools that it can be extremely helpful especially if it’s written an maintained by the author of something like one of the aforementioned issues.
Case in point: WP-CLI and Alain Schlesser.
A few months ago, I reluctantly started to try out using the dark theme that comes with macOS and iOS. I’d already been using a similar theme in my IDE and my terminal, so why not take the plunge for the whole experience across the OS?
Like anything new, it took some getting used to but it’s definitely grown on me up to the point where I spent time looking for something that would allow me to really tweak the tools I used the most to make sure that I’m actually enjoying the day-to-day work that I do.
And that’s where Dracula, hat tip to my colleague Mike England, really got the ball rolling for me.
If you’ve read this blog for any length of time, specifically in the last two or three years, then you know I’m a fan of object-oriented programming especially so in the context of WordPress.
And if you’ve followed me on Twitter, you know that – like many of you – I’ve met many people who I consider to be legitimate friends (versus the bastardization of the phrase by sites such as Facebook)
On top of that, you know one of my favorite past times on Twitter is trolling said friends. So far, though, this entire post is all about my friends and me and, ahem, trolling.
So what’s the point?
Ultimately, it’s to give you a heads up something that’s been released today, that’s been a long time in the making, that’s finally available, and that’s going to help anyone who wants to be a better WordPress developer.
In the first post in this [two-part] series, I talked about the idea of what it means to set a goal. Specifically, I said it was more nuanced than just setting a goal and aiming for it. Instead, I said I thought of doing this:
- set a goal,
- make a plan.
And, if you read the first, you know that I gave an example outside of programming (because I tend to do that sometimes).
But why not also look at what this would look like regarding programming? I mean, the whole point of the site is to talk about how to handle WordPress development from a practical perspective.
And this seems like something that intersects with that whole idea, right?
I’ve talked about productivity and similar resources various times, though sparingly, since writing consistently for the past eight or so years this October (can’t believe it’s been that long).
Though I try to stay true to the whole slogan that I pronounce (that is, Practical WordPress Development), there are times that I like to share things that I think can’t help those involved in the industry that is tangentially related to software or web development.
And in this case, that’s what this post is about; however, I’m going to try to break it into two short reads. In short, the purpose of this is what it means to set a goal, how to go about achieving it, and how to do so both regarding working on self-employment, fitness, or otherwise, as well as how it relates to side-projects (and specifically programming).
I’ll start with the former, first.