Author: Tom (Page 61 of 427)

Gauging WordPress Podcast Interest

January 2, 2019 / Tom

Over the break, I had a lot of time to think about different things as it relates to Pressware and this blog. One of the things I’ve been thinking about for months now is the idea of starting a podcast.

WordPress Podcast Interest

I talked a bit about the initial idea some time ago. In the post, I mentioned the following:

I’m not particularly interested in doing the “interview others” for a podcast because other people are doing them so well and they are interviewing such interesting people.

But I did wonder if there’s not some room for a question-and-answer format. I know many podcasts end their episodes like this. However, I’m interested in experimenting with short podcasts (that is 10 – 15 minutes max) and those that answer questions.

The TL;DR version of the rest of the post is simple:

If you have five minutes to spare, would you mind answering the following survey? It’s not closed to anyone, and this will help me to gauge interest in doing this. All submissions are kept completely private.
The podcast will be short (20 – 30 minutes in length), will have a primary format, and will be geared towards anyone involved in WordPress.

Still curious? Read the rest of the post.

Starting 2019

December 31, 2018 / Tom

I believe last year was the first time that I’ve really spent planning for the coming year and blogged about it. This year, I want to do the same, but it’s a little different.

Starting 2019

Since I spent so much time organizing and planning out how I wanted to get things done last year and since it worked out, all things considered, I want to follow the same format. But the truth is that it’s not nearly as involved since I have a methodology to apply.

In short, it goes something like this (which you’ll see momentarily):

create four specific areas for the things you want to do,
have a set of goals for each of those areas,
if something comes along that both fit in an area and contributes to a goal, do it; otherwise, discard it.

That’s how I operated in 2018, and it’s how I want to operate in 2019.

AOL, Visual Basic, College, Work, WordPress, and More

December 28, 2018 / Tom

Before the holidays (though at the time of this writing, I suppose we’re still in the holidays 🤔), I wrote a little bit about keeping domains, hosting, and email separate. In that post, I happen to mention Kinsta for hosting, as well.

Recently, I was interviewed for their blog as part of a blogging series they’re doing with some people in the WordPress economy.

AOL, Visual Basic, College, Work, and WordPress

Though I never know if these interviews are interesting for others, I always enjoy what others have to share, so I opt to share whenever something like this is published.

Merry Christmas and Happy Holidays (From 2018 To 2019)

December 21, 2018 / Tom

From Christmas to New Years, I’ve typically taken time off of work to celebrate the holidays and to spend time with family and friends.

Merry Christmas 2018

During this time, I usually spend time off of social media and blogging and this year is no different (in fact, I’ve been off certain services for the last month or so save for the work day).

To that end, I’m looking forward to hanging out with my friends and family (and each year gets more and more fun and interesting as the kiddos get older).
Continue reading

Composer Without Continuous Integration

December 20, 2018 / Tom

If you’re a WordPress developer who is using Composer without continuous integration, then odds are you’re left with a crucial step of figuring out how to manage the vendor directory when deploying your plugins.

Composer Without Continuous Integration: Composer

That is:

We know it’s a bad idea to throw the entire vendor directory under source control,
Other developers who are familiar with using Composer should be able to get up and running without the need for much instruction,
Continuous integration isn’t being used for any number of reasons,
And we’re left with needing to provide a production-grade deliverable that uses certain dependencies but not others.

As much as the above points may describe our situation, it doesn’t tell us what we can do with it.

In other words, here’s the use case: You’ve built a WordPress plugin for someone. This plugin uses a variety of dependencies all of which are maintained by Composer.

You’re not checking the vendor directory into the repository, but you’re also not using continuous integration to deploy the plugin. Instead, the customer is, or a third-party is.

So what then?