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!
A while back, I started trying to get more involved with the Linux community again. Back in the day, I was a developer for Arch …
Well, I’m going to start by saying that I’ve failed to make my 30-day mark. Somehow I managed to miss a day without even realizing I did it.
In the world of development, the choice of editors is usually a very personal decision. Some people are minimalists, and some prefer full-fledged IDEs. Some people insist on advanced syntax highlighting, and some prefer good, old-fashioned black on white (or white on black). Not to mention the restrictions that a users’ operating system place on the choice.
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.