Blog

There are basically 3 models for getting web applications built:

• Proprietary platform
• Custom code
• Open Source

"I just want a simple, static website."

OK. Why?

"I don't want to spend the extra money on a CMS. I don't have time to manage a site. I don't know HTML. I just want something quick."

OK.

I get this question all the time: What's the difference between Drupal and Ruby on Rails, or another framework?

What do Twitter, cancer, interviewing movie stars, bike culture, and instant salt & pepper shaker manufacturing have in common? They were all represented on stage at GnomeDex 9 last Friday, a blogging conference on the waterfront in downtown Seattle.

After emptying my camera recently, I noticed a bunch of the photos were cluttering up my home directory. It turns out that the default photo manager for Ubuntu had a bug in the latest release, and while it's fixed for the next major release, they haven't released a fix for 9.04.

When the Olympic Peninsula Tourism Commission came to Freelock Computing to convert their static HTML site into a newly designed, Drupal-driven CMS, I'm not going to lie, a few drops of drool fell from my mouth.

At Freelock, we're big fans of the Dojo Toolkit. It's a Javascript library for providing data-backed widgets in web applications, on-the-fly graphing, animations, and much more.

So once more, development on an internal project hit a stumbling block. The latest release of Dojo, 1.3.1, has some bug fixes I'd like to use, and in general I like to keep my main project working with the newest dojo releases.

Now here's a great video, which pretty much sums up the experience of, dare I say, every web professional?

After receiving multiple requests for a follow-up to my anti-Twitter rant a few months back, I've decided to try and do just that.

One of our clients asks why she's suddenly getting more spam, and what we can do about it.
For a few years, she got no spam at all, and then suddenly she's getting upwards of 80 a week. What happened?