During this years’ State of the Word address, WordPress founder Matt Mullenweg discussed a challenge he had given himself: write a blog post a day for 30 days. While some bloggers, such as the ever-popular Chris Lema can write a post a day with relative ease, I’ve always found it much more difficult to come up with quality content.
WordCamp Tampa is (sadly) over, and I’m sitting at the Tampa airport going over the events of the last few days.
I thought that by now, everyone knew that running random code was generally a bad idea. No matter who it’s from, or where you found it. If you don’t understand it, don’t run it!
I’m sure many of you have already seen it… and yes, it’s a bit dated… but this is by far the best lightning talk I’ve ever seen, and I’m continually shocked at how many people aren’t familiar with it…
This morning, I received a tweet regarding the best conditional widget plugin. This question got me thinking; what is the best plugin? There are several major contenders, but I never really considered which is the right option.
Those of you who know me are probably aware that I’ve got lot of things on my plate. As such, email is a relatively important part of my life.
Every developer knows that sometimes bad code finds its way into even the best products. It doesn’t matter how or why; sometimes it just happens. Lack of sleep, lack of knowledge or plain old laziness are often contributing factors (mostly lack of sleep in my case); but every once in a while I stumble across a block of code that goes above and beyond the occasional poorly coded function.
Recently Pippin (pippinsplugins.com) posted on How to leave a good bad review. For those who haven’t read it, I highly recommend you take a few moments and do so. Unfortunately, the problems present in supporting software are not always the fault of a grouchy end user. In some circumstances, such as the one which inspired this post, the fault lies in the support staff themselves.