Asymptomatic

I've been working on some improvements to Pastoid lately. It started out as more of a response to the URL shorteners that keep popping up everywhere and getting all the press, which Pastoid languishes in obscurity.

For those that don't know, Pastoid is a site that serves two major functions. First, it functions as a URL shortener, like the ubiquitous TinyURL. Second, it functions as a pastebin, like pastebin.com. It has a few little extra features that set it apart, and I have a lot planned for it that will break it out as something really different and special from those other tools.

I recently updated the look of the site. It has been getting mostly negative reaction. I think people don't like the grungy purple. Maybe I'll revise it again, but it does affect the change I wanted where the sidebar is moved to the left to allow code sections to expand in the liquid layout on the right. In addition to that, I've been working on the thumbnail improvement project, which is the true impetus for this post....

My Kindle arrived today while I was watching Riley drive his electric Jeep around the cul-de-sac island. Since he refused to park his Jeep to go inside, I tore open the box right there in the driveway, and carried its contents up to the circle to get acquainted.

The Kindle is an electronic book. It has a paperback-sized screen with a small keyboard below, and large buttons on the sides. When the device is on, it reads just like any paperback book except that when you want to turn the page, you just press the button.

Several special features of the Kindle make it a pretty unique product. I admit that this device is going to be a problem for me because it's just too good....

One of the more common design patterns in installable web applications today is the Front Controller pattern. Unlike other web applications that have separate files to respond to specific requests, the front controller pattern funnels all requests through a single file, and that file processes the requested URL to respond as appropriate.

In typical scenarios, you'll accomplish this with Apache using a set of mod_rewrite directives. These directives first check to see if the requested file or directory exists. If it does not exist, then the request is passed on to the front controller. This allows requests for existing files - like images, stylesheets, and client-side scripts - to be requested directly rather than passing through the URL rewriting mechanism.

If you are familiar with implementing a front controller using Apache, you will recognize these directives, which are commonly found in an .htaccess file within the application directory:...

Man, this week has been difficult. We've had a few server issues with work clients, and I've been playing around with my own servers, and it's just been a mess that I'm hoping will be in the past come next week. But I've learned some lessons, and I figure I might as well pass them on because people are apparently still buying hosting from really bad places.

What do I need? This is the most basic question you need to start asking yourself before you even hunt for hosts. Having some idea of your demands, both from a technical perspective and a logistical perspective can save you some pain in the future. Here are some really basic considerations:

Shared/VPS/Dedicated -- What level of hosting you choose will depend on the types of service you intend to run and the affordability of storage space. Shared hosting is for small, single, low-traffic installations, like a single blog or a low-traffic forum. VPS hosting allows you to interact with the server configuration directly, to host more complex applications and more of them. Dedicated hosting gives you full control over what runs on your system, plus often includes dedicated storage that is many times what you'd get from the other options. But there are more things to consider....

I work on several projects, both for work and for recreation, that require code editing by more than one person at a time. Some projects I've created on my own, while others were well established long before I came upon them. There are common threads between them, and I would like to try to point out some things that I've learned along the way.

When working collaboratively, a source code control system is mandatory. There is simply no other way in my mind to efficiently collaborate on a project of any size without source code management.

One might think that code control is not necessary for collaborating on small projects, but for those smaller projects it is especially true. If a project consists of a single file, and two people are working on that file, the only way to make the changes not continuously conflict with one another is to use some form of code control. The alternative of sending back and forth changes or keeping in constant contact to ask if another person is editing a file you need is not practical....