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 …
As part of the process towards building my bus, I put a significant amount of energy into figuring out how to best handle media while on the road.
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.
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 feel it’s important to note that accessibility is a subject that hits particularly close to home for me. No, I don’t personally have a severe disability, but both my son and his mother do.
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…
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.
A while back, I made a post about conditional widget plugins. After reviewing several, I concluded that the best options were Display Widgets and the commercial Widget Ninja. Well, since then I have discovered another option that wasn’t reviewed in the original post and it has, by far, eclipsed every possible plugin from the original post.