I thought that by now, everyone knew that running random code was generally a bad idea. No matter who it’s from. Or where it’s posted. Basically, if you don’t understand it, don’t run it!
Those of you who know me have likely had to sit through one of my rants on hosting. Anyone who has ever built, managed, or otherwise been involved with a website is sure to know the headaches that can come from finding the “ideal” hosting provider.
Those of you who know me are probably aware that I’ve got lot of things on my plate. As such, email is a fairly important part of my life. I’ve been a loyal Thunderbird user for years now, but recently it has started to show its age (I’ll go into details later on). Given my recent issues with Thunderbird, I’ve spent the last few weeks playing around with virtually every email client I could get my hands on and thought I should share my findings.
So the short of it is this… For the last several years, I’ve been developing independently; releasing my plugins under the name everyone has gotten to know me as: Ghost1227. Fortunately (or unfortunately, depending on your point of view), I have reached a point where that simply isn’t enough anymore.
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.