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.
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 …
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.
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.
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.
If you’ve ever spent any real time working with WordPress, there’s a fairly good chance you’ve run across a strange file in the root (or topmost) directory. Whereas the vast majority of the files comprising the WordPress hierarchy consist of a filename and an extension, such as the crucial wp-config.php
, one single file seem a bit out of place. That file is the aptly-named .htaccess
file. So just what is the .htaccess file?