This week, I finally started using a combination of Bio and Hey World to start pulling together all of the content that I share online.
This blog is obviously primarily devoted to software development and although I considered broadening the scope of it (for longer than you may think), it just seemed easier to use another place and have a single landing page for all the feeds, socials, and so on.
Anyway, that’s the personal stuff I have to share for this week. In the mean time, here are the resources that I found interesting.
TL;DR: Here’s another way to start debugging WordPress with Ray using Composer on a project-specific basis.
Last week, I wrote a brief introduction on Ray, what I like about it, and why I enjoy using it with WordPress. I also gave a brief tutorial on how to use it in your day-to-day but that was it.
Ultimately, I want to cover more about the application from a development and debugging standpoint (as I had some great feedback about it on Twitter – thanks for that!). Before doing so, though, I thought it would be more useful to start with one more tip on how to get started using it.
Namely, how to use Ray with WordPress in a Composer-based workflow.
Most of the resources and articles I’m sharing this week are the usual type but there are a few, such as original Kindles no longer being able to access the web via 3G, that are an interesting read mainly because I remember when the device came out and that was a specifically killer feature for me.
I also started working on a series on how to use Ray to debug features in WordPress. I cover this later in the article.
TL;DR: This post gives a high-level overview of what kind of app Ray is and how to set it up for use in WordPress.
For as long as I’ve been involved with WordPress development, I’ve consistently seen developers – myself included – consistently use print_rand var_dump whenever they need to see what’s going on within their code.
And this is okay for smaller data structures like looks at objects, arrays, and so on. Then on the other end of the debugging spectrum, if you need to step through code to see what arguments are being passed into a given function from where and with what value, then using something like Xdebug is incredibly helpful.
Until recently, I didn’t think there was middle ground. But then I found Ray and I’ve been using it ever since.
This week, I clocked out of my role as a Senior Backend Engineer at WebDevStudios (and it was a great 2.5 years of solid work on some very interesting projects), and began working as a Senior Developer at Awesome Motive.
I’m sure I’ll have plenty to share as I settled into the new role but, until then, I here are some of the resources I’ve found over the week: