Software Engineering in Web Development, Backend Services, and More
Now that all the rage that responsive design has become a bit more common place in our day-to-day work, I think it’s worth sharing how to test for responsive design.
Specifically, this is how I think a lot of us has historically tested for responsive design:
Testing Responsive Design
It’s funny because it’s true, right?
But here’s the thing: Is this really a viable use case for properly testing responsive design?
Comments are closed. Congrats to those who entered, and read on to get 30% off of the Power Plan.
Last week, the guys and gals over at InMotion Hosting were kind enough to offer a year of free hosting for their Power Plan, and one year of free hosting from WebHosting Hub.
The winners for each of the prizes, respectively:
Congrats to those guys!
If you entered the contest and are still looking to InMotion Hosting as a provider, then they’ve been kind enough to offer a discount through this site.
The WordPress Plugin Boilerplate has been a bit of a pet project of mine a little over the past two years.
In that time, it’s grown from something that I was using to jumpstart my own plugin development efforts into a more mature boilerplate that provides a significant number of features specifically to help developers get started with best practices in developing WordPress plugins.
However, that maturity has happened not because I’m the one who has been constantly contributing to the project, but because it has received so many awesome pull requests and discussions from others.
And with my getting ready to release `2.6.0` of the Boilerplate, I’m looking for one final push!
Note that I no longer use SpiderOak Hive. You can read more about this in the comments of the post.
A couple of months ago, I came across an interesting article by Doug Belshaw that covered his thoughts and experiences with Dropbox, SpiderOak Hive, and why he made the jump from one to the other. In short (and straight from his blog):
I’m moving from Dropbox to SpiderOak for file sync/backup. SpiderOak not only encrypts files in transit, but on their servers. The encryption key stays on the user’s machine so SpiderOak employees (or anyone else) can’t get access to your files.
Shortly after reading the article, giving it some thought of my own, and taking an in-depth look at SpiderOak, I ended sharing the following:
so i made the switch and am giving spideroak hive a try. keeping dropbox free, but everything else is going into spideroak.
— Tom McFarlin (@tommcfarlin) August 29, 2013
My current setup – as mentioned – is the free Dropbox plan (with which I have 6.2GB of space), and a SpiderOak Hive subscription for 100GB. It’s been just shy of two months, so I thought it was time to follow-up with my experience thus far.
Over the past few years, we’ve seen the rise of a number of different publishing platforms.
What once originated with Xanga and LiveJournal gave way to Blogger (or The Artist Formerly Known as BlogSpot), WordPress, and which has now opened the doors for platforms such as Medium, Svbtle, Ghost, and so on.
To say that we – as a culture – are exploring the various forms of digital publishing in as understatement. But one thing that I’ve begun to notice about some of the newer platforms is the way that they handle comments.
On top of that, I’ve also begun to notice that people appear to be commenting less on blogs – at least in longer forms – and taking the discussions more to places such as Twitter, Google+, or even just into email.
Some of this I’m speaking based on observation, some of it I’m speaking based on experience. But I do think it raises the question as to if we should consider how we handle comments on our blog.
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.
© 2026 Tom McFarlin
Theme by Anders Noren — Up ↑
