Author: Tom (Page 76 of 428)

Developer Fitness in 2018: Quarter 2

July 26, 2018 / Tom

Apparently, with the exception of my previous post, this is turning out to be my week to share things related to the second quarter of this year (the first being about taking some time off of social media).

Earlier this year, I talked a bit more about why I think it’s important for we, as developers who spend so much time at a desk, to focus on our health as well. Granted, this is has been compeltely focused on my own goals.

Specifically, I said:

The purpose of this post is to go a bit further into what my goals have been first the first quarter of the year, what I’m aiming to do in the second phase of the year, and some additional thoughts on the devices I’ve been using.

But this doesn’t mean it can’t translate into your own life in some capacity, right? I’m the last to say that “what works for me will work for you” because I think our body composition plays a massive role and we’re all different.

Anyway, if you’ve not read what I’ve written thus far, check out these posts first (if you have the time):

Even though I’m a bit later than planning for writing my second quarter retrospective, here it is, nonetheless.

Reading and Understanding WordPress Error Logs, Part 2

July 25, 2018 / Tom

Last time, we walked through the following:

configuring debug constants,
locating an error log file,
understanding how to read the log file,
understanding stack traces
understanding how to read the stack

As nice as that is, it’s still important to understand how to write data to error log from a programmatic aspect. That is to say; it’s one thing if your work throws errors, warnings, or notices.

Understanding WordPress Error Logs

It’s another thing if you want to understand how to write information to the file for research and debugging manually.

In this post, we’ll continue doing exactly that to further our understanding WordPress error logs.

[restrict paid=”true”]

The Second Social Media Sabbatical of 2018

July 24, 2018 / Tom

As I’ve been writing this post, I’ve felt so pretentious when it comes to using the word “sabbatical” as it relates to something like social media.

I mean, I’ve always associated sabbaticals as something that professors, academic types, religious leaders, and higher-ups take. Not just an average dude who makes a living on the Internet.

Sabbatical or a sabbatical (from Hebrew: shabbat (שבת) (i.e., Sabbath), in Latin: sabbaticus, in Greek: sabbatikos (σαββατικός), literally a “ceasing”) is a rest from work, or a break, often lasting from one month to a year.

But I suppose, by that definition, it makes sense, right?

Anyway, I started the trend earlier this year, it went well, and I want to keep a consistent theme going at least for 2018, so why stop it during just the second time through?

What’s with the ERR_SPDY_PROTOCOL_ERROR?

July 20, 2018 / Tom

One of the things that’s often brought to my attention is that people see the ERR_SPDY_PROTOCOL_ERROR whenever they try to access this site.

ERR_SPDY_PROTOCOL_ERROR

I’ve had people respond to links from my newsletter, from links on Twitter, from links from third-party sites, and sharing their experiences when trying to access other sites, too.

The thing is, few people – myself included – seemed to be able to diagnose the problem. (And believe me when I say that I’ve tried a ton of different things to fix it on my end.)

So to the best my ability, I researched the problem, all possible fixes, and thought I’d share what I found here along with the fixes.

Reading and Understanding WordPress Error Logs, Part 1

July 19, 2018 / Tom

As we continue looking at what it means to be an independent WordPress developer, the tools needed, and the various strategies that can improve our skillset, I’ve been talking through the various constants, plugins, and tools to help us.

If you’re just stumbling across this post, then I recommend checking out my guide to native WordPress debugging tools as well as the rest of the posts in the series thus far.

After all, I find it important that we’re all working off of the same foundation – or something closely related – when going through this information.

Understanding WordPress Error Logs: Xdebug

Ultimately, using a tool like Xdebug is indispensible, but we have to work up to that (for those who are curious, I wrote a brief guide about this a little over a year ago).

For now though, let’s start with the basics. In the previous post, I left with the following statement:

In the next post, we’ll start looking at what’s necessary to examine the error log that’s generated by WordPress and how to understand the information we see.

And that’s what I want to look at today because, if nothing else, it will give you something practical off of which to work.