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?
Continue reading “How to Set a Goal, Part 2: We’re Writing Code Setting a goal is one thing, making a plan to achieve it is another. And that lends itself precisely to what we do for a living.“
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.
Continue reading “How to Set a Goal, Part 1: We’re Not Writing Code Setting a goal is one thing, and it’s admirable. But I think there’s more nuance to it than that.“