Author: Tom (Page 126 of 428)

You Should Come to WordCamp Atlanta 2017

January 27, 2017 / Tom

Last year, I had the opportunity to attend WordCamp San Diego, WordCamp Atlanta, WordCamp US, and several local meetup groups and enjoyed my time at all of them. This year, I’m trying to spend less time attending conferences and speaking for a number of reasons (all of which really have to do with wanting to focus on work-related stuff).

WordCamp Atlanta 2017

Since I live just outside the city, though, I’ll be at WordCamp Atlanta 2017. Further, I’m looking forward to speaking on the developer track.

Sharing Our Programming Problems (Is It Lipstick on a Pig?)

January 26, 2017 / Tom / 0 Comments

I was recently reading another programmer’s blog post on Coding skills you won’t learn in school in which he was specifically talking about Object Ownership. The topic of the blog post is good in and of itself, and if you’re into lower-level programming, such as C, and data structures, like trees, then it’s worth a read.

Programming Problems: Object Ownership

But just as I was closing the tab, I came across the following paragraph at the bottom of his post:

Broken software, bad job offers: I”m sharing my mistakes so you can avoid them.

In short, it’s an invitation to join his mailing list (which is fine), but what really caught my eye was his call to action:

I’m sharing my mistakes.

For anyone who writes on the web – myself included – I think a lot of us do share our mistakes, but I couldn’t help but think about the way we go about doing it.

And it now has me re-thinking the approach to some of the posts that I’ve written and that I’ve yet to write.

A Bit About Micro.blog (And Why I Backed It)

January 25, 2017 / Tom

In a deviation from the typical type of content I write, I want to share a bit about Micro.blog in case others have yet to hear of it, why I backed it, and what I hope it aims to do for the web.

About Micro.blog: The Kickstarter Page

In short, the whole purpose of Micro.blog is to provide an easy place for people to both write and own their short form content.

From the Kickstarter page shown above:

Today, most writing instead goes into a small number of centralized social networking sites, where you can’t move your content, advertisements and fake news are everywhere, and if one of these sites fails, your content disappears from the internet. Too many sites have gone away and taken our posts and photos with them.

And the service is targeting services Twitter, Facebook, and other similar sites. Don’t get me wrong: I like and use Twitter, but I also know that whatever it is I post there is up to the discretion of the service on if the content persists.

But there’s more to it than that. At the time of this writing, there’s a week to go in the Kickstarter, though it’s far surprised its goal, there are some things about the service I’m excited about and want to share.

Temporary Options in WordPress: Our Best Option?

January 24, 2017 / Tom / 0 Comments

When it comes to programming, the idea of temporary values or temporary variables or any way of storing data temporarily in memory isn’t anything new.

But when working with WordPress – which is stateless – we don’t always have that luxury. That is, it’s not simply a matter of, say, throwing something into the current session, reading it, and then removing it when we’re done with it.

And that’s when I’ve been giving more and more thought to the idea of temporary options, for lack of a better term of course. That is, whenever I need to store a value from a single page load, or request, to read in another page load, or another request, I’ll temporarily throw the value into the options table.

Temporary Options: An Exercise and Representation via Rudimentary Sketching

Is that sloppy? Maybe. Do we have a lot of other choices? It depends on how much of modern browser technology we want to use. That’s not the point of this post, though.

The point is that because of the way WordPress works, I wonder if our current, best strategy for maintaining temporary values that is most widely supported across installations is to temporarily add a value into the options table, read it, and then delete it once it’s been retrieved?

When To Use WordPress Subactions (And What Are They?)

January 23, 2017 / Tom

I recently walked through the process of using a class’ constructor to prevent a plugin from working if it an expected dependency isn’t loaded.

Though I don’t consider this particular strategy a problem for a one-off dependency or in certain situations, there are ways this can lead to code smells.

It also prevents us from using a native feature of Core called WordPress subactions:

https://twitter.com/JJJ/status/822265137935646720

But before looking at subactions, I want to make sure I’m clear around the problems using the conditional approach (versus subactions) can breed with code smells.