A one-for-all, all-for-one solution to website content management is the holy grail of my profession. For my web development work for clients, I find that several of them have a lot of specific features they want in their content management system (CMS). But soon enough I’m walking the tight rope between simplicity and flexibility.

Selecting a tool to build such a website or application is a matter of audience. The first audience, software developers, need either a lot of freedom or a lot of options. In practical terms, for my PHP development, this is a choice between CakePHP and Drupal. Working with both of these equally has been eye-opening, because without fail there are many features that are much faster to implement in one or the other—it truly ends up about 50/50. Want to display a custom calculation in a specific place on the site? With CakePHP it’s simple. Want a paged image gallery with Lightbox functionality? Drupal can get you there much more quickly.

For both these platforms, the other audience comes into play as well, namely the client. Obviously the client needs to have their available options presented as concisely as possible—they don’t need (or want) a huge amount of freedom or options. So the creation of such a simple interface falls to the developer. The trick is knowing which stuff to allow them to change and which stuff to hard-code. In both cases, priority #1 is defining these as variables (or object properties) as soon as possible in the code, so we can switch back and forth if need be. Yet clients will always possess an uncanny knack for requesting the tweaks that are most troublesome to implement. Granular permissions, anyone?

Creating robust software that is still easy to use is the challenge facing any software developer. Apple has rightly gained a reputation for striking this balance with substantial success, yet they are certainly not above reproach. In the web industry, the balance of power is more volatile, as anyone with a great idea can launch a web application with little to no concern for infrastructure—innovations from Google, Rackspace, Amazon, and the like are taking care of those issues. And while there are a wealth of options in the realm of content management, several of them quite good, I believe this abundance indicates the ongoing problem of balancing features with simplicity in these applications. After a myriad attempts, the world still awaits a truly excellent CMS.

NOTE: Parts of this post were originally a comment at Gadgetopia.

This new “activation model” is patently insane and just made my life 100 times more difficult. If someone were to create a fork of Firebug 1.3 that preserved domain whitelisting/blacklisting, I would pay $50 for it easily. johnjbarton [the resident firebug developer], since you seem oblivious to how the new version is problematic, let me spell out some common scenarios I have tried:

Previously I enabled firebug for localhost, since that’s where I do most of my testing and developing. Then I would browse from page to page (without the panel open) until the “script error” message came up on the status bar. Then I’d open the firebug panel and troubleshoot. I’d fix it then perhaps browse around a few more pages, with the panel still open. When I was happy I’d solved the problem, I minimized firebug (back in those halcyon days, I could click the “x” button or the little firebug icon to remove the panel—it didn’t matter). But firebug stayed active, so I would be alerted to script errors if they happened.

Fast forward to today. Seems firebug now remembers panel position PER PAGE, which is ludicrously stupid. So as I browse from one page to the next, the panel is randomly disappearing and reappearing. And of course I can no longer simply tell firebug to be active only for localhost. WOW, WHAT SOME GREAT NEW FEATURES, GUYS!

The new system is completely absurd, and I hope now you can begin to see why. When a tool as ubiquitous as firebug gets changed so drastically, the question is WHY? We all loved it before, so please stop butchering it. And again, I put out the call to some developer out there who would want to continue the awesomeness of firebug 1.3 and perhaps rename it. That person would be regarded as a hero at this point…

I received an immediate response that at least acknowledged the legitimacy of my point of view:

Work on Firebug 1.4 is complete. Your scenario description is a good one, I wish we had it back when we were working on this feature. I’d love for Firebug to be perfect for everyone, but in every change there will be some winners and losers I guess.

The activation model in 1.4 was designed to allow extensions to provide special activation solutions.  If anyone wants to create one for this use case we’d be happy to give advice. (Just to set expectations, I have no plans to do any more work on activation myself).

As you can see, it seems this train is already moving at full speed, and those of us who loved the way Firebug formerly behaved will unfortunately have to endure (for the time being) the headache it has become. We can only hope a proper “extension” is released that brings back the wholly intuitive domain-based activation scheme that worked perfectly before. Until then, a single tear shall roll perpetually down my cheek.

An application I’m developing at work runs critical code in beforeFilter() that checks if a user is logged in and uses the results to set the website title and which links appear in the main menu. So you could say that’s fairly important. But on my error pages, Cake would conveniently display no title or main menu whatsoever. Because no debugging messages were displayed, I thought the issue might have been a minor case of a different layout file being used for error pages. But after a thorough combing of Cake’s library code, I discovered the ugly truth within the cake/libs/error.php file: the CakeErrorController class, which is used by the accompanying ErrorHandler class, never calls the beforeFilter() function. This contrasts with the Dispatcher class in cake/dispatcher.php that is responsible for most normal pages—this code eventually runs beforeFilter() within the controller’s _invoke() function, but before that it also calls the controller’s constructClasses() function, which turned out to be a critical part of my solution to this now unwieldy problem.

After attempting several ways of making the error pages run my beforeFilter() code, I found that simply adding $this->beforeFilter(); as the last line of the CakeErrorController constructor seemed to work. The problem with doing this, however, is that I had to change a core file within Cake. As my fellow developers know, this is not an option, so I had to make it work from within my own code. But luckily I was on the right track: the constructor inherits from the AppController constructor, which I was free to modify. So within my application’s app_controller.php file, I added a constructor and copied the code from CakeErrorController, making sure to add my call to beforeFilter() at the end. Amazingly it seemed to work, so I then proceeded to see which lines I could safely comment out, until I was left with just a few lines of code. The constructClasses() function in particular seems to be Cake’s succinct way of loading the components used by the application. After testing several normal pages and error pages alike, I feel fairly confident that I have solved my initial problem. Here’s the code I added to app_controller.php:

function __construct() {
    parent::__construct();
    if ($this->name == 'CakeError') {
        $this->constructClasses();
        $this->beforeFilter();
    }
}

Since I was forced to put the code in the main AppController class, some side effects may exist: beforeFilter() is potentially called twice on standard pages and perhaps earlier than normal. From what I can tell, this doesn’t affect the application’s performance or behavior. So hopefully this solution will help other CakePHP developers who want their error pages to behave as expected. But surely I am not alone in hoping that future versions of CakePHP will make this workaround unnecessary.

UPDATE: I tweaked the code to include an explicit check for CakeErrorController before running the extra lines of code in the constructor. I found a fail case that had to do with adding new users via the Auth component—new passwords were being hashed twice. So this new snippet should successfully eliminate the possibility of code running twice needlessly.

I had a pretty good feeling about things the moment I landed in the midst of pristine weather on Sunday evening. My hotel, which I chose seemingly at random, was situated a stone’s throw from South Beach. But the room itself was distinctly lacking in frills—an unassuming king-sized mattress bore the weight of my imminent slumber, and a clunky television relayed lackluster imagery from a limited supply of channels. I half expected Max Headroom to show up on this war-torn monitor, but before he had the chance, I was out cold. The operative word here is “cold,” for I awoke a bit earlier the next morning than I would have liked, thanks to the icy air flowing freely beneath my sheets. Next stop: free breakfast in the lobby.

The impressive stage of the main conference

I have to say that the bagel and cream cheese were exemplary, though the same cannot be said of the coffee. Soon enough I called for a cab to take me to the main venue, and whilst waiting met Baltimore’s own Javie Rios, a web designer who, I discovered, shall attempt to represent the U.S. in the 800 metres at the next Summer Olympiad. We arrived at the Adrienne Arsht Center and began our first of two workshops for the day. I really had no clue which of these workshops I would be attending, but eventually ended up at the one concerning the Social Web, specifically the paradigms of OpenID, OAuth, and Activity Streams, among others. This proved quite valuable for me, a bemused veteran of the current OpenID system, a noble concept that is racked with irritations. But I greatly enjoyed hearing David and Chris explain where they’ve been and where they’re going—how such stalwarts as Google, Yahoo, and now Facebook are all on board with this emerging system of ubiquitous user management, and how it will one day be much easier for all of us to log in and share information easily between all of our websites and services. The standard interface for logging onto sites using OpenID has been admirably refined, although pop-ups are still favored over AJAX boxes so that the user knows precisely which URL is asking for his password. An idea that popped into my head at this time was that no source is more trusted than the browser itself, so I would love to see OpenID login integrated with the major web browsers as soon as possible. The ideal scenario for OpenID would certainly make life vastly easier for both users and developers on the web.

At this point the conference attendees were rewarded with a yummy box lunch featuring a sandwich wrap and other trinkets. During the break, I met Sam Thomsen, a .NET developer from Denmark who, along with his coworkers, had parlayed his visit to Miami into a full-blown vacation. Good call, huh? I then ran into Nikki Scoggins, a sprightly gal who works for Vans and is responsible for their various social media efforts. In the midst of our discussion, a friendly gent by the name of Ryan plopped down beside us and expressed his keen interest in the Vans brand, himself wearing a distinctive green pair from the venerable shoemaker. Only after a couple of minutes did I realize that this Ryan was the selfsame Carson who is responsible for the entire event, so I credit that to his approachable and friendly nature (and a bit to my own obliviousness). I was able to talk to him a little about my employer Merge, and how I left in the midst of a site launch to be here, a fact he duly appreciated.

Now it was time for workshop number two, a presentation from Wufoo‘s Kevin Hale about how to convert free customers to paying customers on our web applications. A few things stood out to me here. One: display all paid functionality on each page, even to free customers. People won’t buy it if they’re not aware of it. Two: try to stay away from coupon codes. Studies show that people will abandon their shopping carts when they see a coupon code box, because it clearly shows that they could be getting a better deal—those shoppers may leave to find a code but won’t return if they don’t find one. Additionally this workshop also provided a good synopsis of analytics tools like Crazy Egg and ClickTale that can effectively show how visitors are using your site. And perhaps most enlightening was the comparison of the relationship between your business and your customers to the marriage relationship, specifically the theories of Dr. John Gottman and how you can greatly enhance your company’s reputation by engaging in open and honest communication with your users, a strategy employed with great success by Zappos.

Day one’s official events had drawn to a close, but there was more to be done. In the Arsht Center lobby, I met Romain, a web developer from France who has worked on a pretty nifty app that lets his customers provide precise feedback by clicking on specific areas of a screenshot and leaving relevant comments. I spent a fair amount of time with Romain and really enjoyed discussing the differences between our countries and the challenges of working for a small business that are specific to each. (Special note to Burger King: you are greatly missed in Paris and would be welcomed back with open arms.) Before heading back to my hotel, I joined Javie, Romain, and Avin for some quality grub at Mike’s at Venetia—I devoured my “dolphin sandwich” with a true sense of purpose. We enjoyed an hour or two of excellent conversation, capped by my request for some bands that I should be listening to (American Head Charge, Switchfoot, and The Used, apparently). My suggestion for them? Plaid’s Double Figure.

I was definitely ready for sleep, and sleep I did. But the next morning, things would take a turn for the weird. My room phone rang a little after 7:00 in the morning, a half hour before my alarm was set to go off. I ignored it, but then it rang again. Bemused and confused, I answered. “Hello, sir,” said the lady at the front desk. “I’m sorry to bother you, but the gentleman next door to you needs to get into his room, and his door lock malfunctioned. Would you mind if we came through the connecting door in your room?” Before I had a chance to consider that opening his connecting door from my side might prove just as challenging as opening his main door without a key, I agreed. Within minutes, the woman and the guy in question, both likely in their twenties, entered the room and began discussing the situation in Spanish. As I stood beside my bed with mussed hair, raggedy shirt, sweatpants, and doubtless a face betraying extreme befuddlement, the guy opened my connecting door then proceeded to launch a full shoulder charge into his connecting door. He repeated this about twelve times, with brief interruptions punctuated by additional Spanish dialogue. Eventually the door cracked then burst open, presumably solving the immediate problem but creating a new one for future concern. Now that I was fully awake, I showered, dressed, and went downstairs to enjoy another scrumptious bagel.

Puerto Sagua = Best. Cuban Food. Ever.

Javie and I caught a taxi again and arrived for the start of the main conference itself. The auditorium was impressive, and the audience was eager for the show to start. Ryan came on stage for a brief intro, and before long we had our first speaker, Jason Fried of 37signals. Jason has a penchant for making controversial statements on his company’s blog, and while I disagree with him about half the time, I appreciate his willingness to take a stand on things. His major point during his speech was that web developers should stop giving away our work for free. Open source software is a popular movement, and it’s not going anywhere, but just because a big company like Google or Mozilla can give away stuff for free doesn’t mean the rest of us should necessarily follow suit. Even if our direct competition is open source, the market is still big enough for companies that charge—there are plenty of customers for everyone. Also we should look for opportunities to sell our “byproducts.” In the case of 37signals, these take the form of knowledge shared in books and conferences, each with price tags attached.

Next up were Ben and Dion, a couple of guys from Mozilla who talked about the future of the web browser. They discussed a quartet of exciting features, some of which are already in place for many browsers: Canvas, fast Javascript, web workers, and desktop integration. Following them was Dan from Yahoo Developer Network, who discussed such technologies as the YUI library and YSlow, the latter tool which I have consistently found very useful. We were then dismissed for a lunch break, so after a quick trip to Burger King, I returned to the facility and crossed paths with the lovely Jeile Marie, host of Go Live Miami, a series of fun webisodes about the plethora of events in the area. Jeile had actually come by our table the previous night at Mike’s and told us a little bit about her site, so I enjoyed the chance to have a longer discussion about the event and our respective backgrounds. I’m still cracking up as I think of the “Hot Lips” shirt she was wearing. Hopefully I was able to give her a few good pointers as she continues her video projects. (Hint: start networking with iJustine if possible!)

The next wave of speakers began with Joe Stump from Digg, who had some nice ideas about how to construct development teams—holding them to under 10 people is a start, but of course you can have multiple teams. He also implored us to use version control if we are not already. I myself have used Subversion in the past but would love to start using Bazaar at Merge. Also heavily endorsed was the concept of unit testing, a bridge I have yet to cross but am sure to encounter at some point. Next on stage was Kristina from Brain Traffic, who expounded the importance of good web copy then initiated a discussion about the still lackluster presence of women at web conferences. She had a good attitude about the matter, but all agreed that it will take continued effort to get more female voices on stage. Really though, this is a problem that has been a part of all computer science industries since day one. There may be something more physiological at play here that none of us fully understands yet.

Aza from Mozilla was our next presenter, who talked about the “chaordic” workflow (ordered chaos) that drives innovation at Mozilla. He identified five directions the web browser space could take in the next five years: people will become more important than technology, common tasks will become more ambient/low-cost, the browsing experience will become more continuous between desktop and mobile, tabs will graduate to a more user-friendly “2.0″ interface, and functionality will be customizable by the use of technologies like Ubiquity. Our next speaker was Dave Morin from Facebook, who touched on Facebook Connect and outlined three features of the social web moving forward: identity (give users control and trust), friends (give users the power to connect with each other), and feed integration (promote openness in your web applications).

What happened next could be classified as the obligatory dud of the conference, and appropriately enough the hapless Microsoft found themselves at the center. The company put on some sort of web app design challenge about space travel called Phizzpop, and we the audience witnessed the presentations of the two finalists. The first was a group apparently comprised of college students, with the peculiar brand of awkwardness that can be expected from this age group. Still, they achieved more success than the second group, which was made up of what might be considered the stereotypical programmer types. There’s really no need to say too much more about this contest, because none of us really knew what was going on or why it was happening. But a hearty congratulations to group one for emerging victorious.

Joel Spolsky then took the stage and delivered a somewhat dry and wry speech about “development team nirvana” and how his company has structured its office space to promote this goal. The key elements of this initiative were separate offices for each programmer, snacks always within a close radius, and ample money spent on proper chairs. Team lunch outings were also heavily endorsed, so it’s nice to know that Merge is doing its part to help me achieve self-actualization. Next up was Dave McClure, who was not afraid to perpetrate garish fonts and colors on the audience in order to make his point about how to grow and maintain your user base: acquisition, activation, retention, referral, and revenue. Concentrate on executing your plan in that order, and you too will find multicolored success… or something. Rounding out this portion of the lineup was Alex from Virgin, a company with a truly distracting name that yet manages to plaster it on every conceivable type of product. Needless to say, this presentation was about the importance of your brand. Key point: in the age of the web and social media, more people than ever are equipped with B.S. detectors (and I think mine may have started going off).

The Nikki Beach after-party. Good times.

Okay, only two speakers left, and by all accounts they were the stars of the show. First, the initially unassuming Francisco began talking about his company 280 North but in no time flat was bringing the house down in uproarious applause. The reason? Atlas, a graphical IDE front-end for Cappuccino that allegedly allows developers to construct layouts and incorporate logic for instantly cross-platform web applications, potentially alleviating developer frustration with tweaking apps for IE and iPhone. The demo was admittedly impressive, and I for one wish them nothing but luck in bringing it to fruition. I asked Francisco later about back-end database support, and he indicated they would be aiming to ship Atlas with some built-in database management, but it’s still unclear right now how much code the developer will be required to write by hand to hook into, for example, existing MySQL tables.

The last man to take the stage was someone whom I had only seen previously on Late Night with Conan O’Brien as a whacked-out “wine expert” who wanted Conan to eat dirt and other miscellany in order to develop his palate. Yes, friends, I speak of Gary V. Apparently he also has a thing or three to say about making your mark in your chosen industry and taking advantage of trends and opportunities in business. His basic advice is to hustle (or more creatively, “crush it”) if you want to succeed. “Passion is undefeated,” he says, and with this I agree. He said several other things, and said them as colorfully as possible, so if you’re ready for an aural assault, feel free to check out his pep talk for yourself.

Whew. I certainly was not alone in feeling like I had just absorbed a heapin’ helpin’ of quality information that would last me for another year, so the rest of the evening was dedicated to relaxation and fraternizing. Romain and I walked over to the bus station, where we combined forces with Nikki (with whom I might have the opportunity to collaborate on a project—stay tuned) and our new friend Victor from Philly. When we got back to South Beach, I discovered that Victor had a significantly superior hotel room despite paying a similar rate. Sure, it was a little farther from the major clubs and such, but it had a widescreen TV and a box full of assorted sweets and treats! Anyway, whilst Victor met up with another friend, the remaining three of us ate at a wondrous Cuban cafe named Puerto Sagua, where I feasted on a mixture of Spanish ground beef and rice, with black beans and fried plantains on the side. This meal was approximately 100 times better than my sole previous Cuban dining experience, and I would recommend it to anyone visiting Miami Beach.

From here we eventually made our way to the official FOWA after-party at Nikki Beach, a place which I’m fairly certain would possess a slightly different atmosphere on nights when a swarm of web developers have not descended upon it. I say this because I had been informed earlier by Jeile that their standard dress code falls squarely into the category of posh. Speaking of Jeile, we were able to meet up again here, and she kindly expressed her gratitude for my helping her get the lowdown earlier in the day about the conference happenings to that point. We talked a little more about the stuff she was shooting for the event, and I helped her track down Jason Fried for an interview. I do believe the resulting video is now online at Go Live Miami, so enjoy! Meanwhile Romain and I started a table that progressively grew in size so that it eventually resembled a giant poker game. Thanks to to Nik and Chris from Enso CMS, Avin and his wife, and everyone else who dropped by the best table at Nikki Beach!

Couldn't complain about this

Luckily my flight out of Miami the next day was scheduled for the afternoon, so I was able to spend a lazy Wednesday morning walking up South Beach and savoring the cool 71-degree temperature and sunny skies. As I paced barefoot through the sand and the water’s edge, I began to notice a particular feature of the beach that I had not anticipated. Indeed I speak of topless sunbathing, an activity enjoyed by no less than four participants during my roughly 45 minutes spent patrolling the area. It must be pointed out that each of these women was equipped with surgically enhanced wares that she was probably eager to showcase for others, and given the price tag of these acquisitions, such motives are understandable. Still, I think the ladies of the world may benefit from the observation that most guys, myself included, would prefer your natural beauty unretouched by scalpels and silicone.

At last it was time for me to leave this vacationer’s paradise, to bid Miami and its beaches and its hot pink signage adieu. Romain and I caught a cab back to the airport, ate some deliciously greasy American pizza, and lounged at the terminal until my flight was ready to board. I took my seat on the plane, broke open my recently purchased copy of Dante’s Inferno, and was impressed by a few recurrent themes from the conference. Fellow developers and entrepreneurs, I leave you with the words of Dante’s Virgil:

What is it, then? Why stand here, why delay?
Why let such cowardice come take your heart?
Why are you not afire and bold and free?

And Dante’s response:

Your words have put my heart in order now,
kindling so great a longing to set on
you’ve turned me to our first intention—go!

1. Retweets — The concept of retweeting does not bring me joy but unfortunately seems to be an accepted practice. It occurs when people post another individual’s Twitter message verbatim, typically adding the letters “RT” to the front, which at least alerts me to the distinct probability that I have read this before. You see, the likelihood is all too high that the “retweeter” and I both follow the same person, rendering the repetition pointless. Plus I have a long-held belief that the world needs more original thought, and retweeting obviously flies in the face of that. I want to read YOUR thoughts, Twitter friends, not rehashes of someone else. If you would like me to follow someone whose tweets you think I’d enjoy, feel free to suggest. But please stop liberally borrowing their work for your own entries! And lest I forget, retweeting has an even more gruesome manifestation where people actually repeat themselves, typically within a day of the original tweet. This, ladies and gentleducks, is unacceptable.
2. Syncing Twitter with Facebook — Folks, folks, folks… This one falls directly under the category of “Cool! This can be done, so I’ll do it!” We human beings are prone to engaging in numerous activities solely because they are technically possible, regardless of how pointless they may be. Proofs of this theorem are readily available. In all likelihood the amount of overlap between your Twitter friends and your Facebook friends is inordinately high, meaning most of us are getting a double-barrel blast of your latest thoughts. Now I know this repetition could prove valuable if I’m ever tested on my memory of transient thought-nuggets generated by all my comrades, but really, people. Unless an online version of Don’t Forget the Lyrics: Social Network Status Edition happens to sprout from the ether, all of this doubly generated text will probably serve no ultimate purpose. (Note to self: create Don’t Forget the Lyrics: Social Network Status Edition to profit from this annoyance if it continues…)

Anyway, these are my two cents on the matter, and I do realize that these oddities happen primarily because they are allowed to happen. The situation reminds me of the ferocious Worms 2 matches of a bygone era—one day I realized that it was possible to kill an opponent’s worm in one move merely by the skillful placement of a common red grenade. This wrought much consternation from my ill-fated adversaries, and they pleaded with me not to resort to such “cheap” tactics. “But the game allows it, and you can do likewise,” I retorted. Granted, I still feel this way, but I exhort you, Twitter user, not to follow in these ill-begotten footsteps. I encourage you to do what is right and rise above the game.

Klection gets its data from Freebase, which is a tool similar to Wikipedia but much easier for other websites to access, and which also allows you to correct erroneous or incomplete data yourself if you happen to notice any. I’m running the site on Google App Engine, a hot-off-the-press framework that enables Python developers to build very scalable sites that employ Google’s infrastructure. So without further ado, go give Klection a try, and let me know your thoughts.

Much like the previous iteration, this one was coded and styled in a flurry within only a couple of days. But the ideas have been stewing for a while. I knew I wanted bold contrast, larger type, a liquid layout, and a design that plays to my strengths. I’m pleased with how things came together, although WordPress’s methods of dealing with site domains and image URLs assured the redux wouldn’t happen without a fight. But I do like WordPress, particularly its seemingly new feature of finding the correct URL if you enter one that is slightly different.

The big thing for me was organization and placement of content and links. Prioritizing based on text size and color is at the heart of the redesign, and I spent much time thinking over it. Hopefully the many things I’ve learned since working at BigBlueHat are evident in the logic behind the site’s new layout. Eventually I just needed a primary color, and what better choice than my lifelong favorite: red? I’ve also added my “greatest hits” atop the left sidebar and placed links to my social networks at the top right of the site. Moving forward, I plan once again to incorporate randomized photos in the upper left, and I need to check the links from past entries for current validity. I’m also considering some widgetized content above the footer, such as my Amazon wish list or Picasa web albums. I have even debated whether to join Twitter at long last so I can have some up-to-date content in the currently empty upper right, but we’ll see.

So that’s the whole mundane tale. The timing of this redesign was quite unexpected, but after a truly bizarre last couple of weeks, I felt a sudden urge to pool my creative energies into something fun and, at least to me, worthwhile. I’d be glad to hear your thoughts, especially if you find something weird.

1. BigBlueHat — This is the two-man shop where I work. Ben and I blog pretty regularly about everything from CakePHP to donuts, so you will surely not want to miss out on the latest developments in these and other critical areas.
2. Chuck Norris Hiking — Some friends and I set up this blog for our California hiking and sightseeing excursion during the summer of ’07, but since we have the domain, I am sure we will blog during future exotic vacations as well. Tentative plans call for a sweep through Seattle and Vancouver this summer, so stay tuned.
3. Lousy Movie Night — This is the latest and greatest of my collaborative blogs, established in honor of what has become a Friday night ritual: the viewing and denigration of the dumbest films in cinema history. A large group of us has been assembled to provide this public service to you free of charge. Remember, friends don’t let friends watch lousy movies alone.

Oh, did I mention we back up all of our code via Subversion, and therefore I didn’t really “lose” anything? I suppose that’s an important detail, although it severely hampers the dramatic impact of my anecdote. And I really did lose my Firefox particulars. But this ended up being a blessing in disguise, as once I had my current system up and running I was forced to commence the bookmarking/adding-on process anew, and uncovered some possible reasons for my aforementioned browser troubles—namely, another session manager extension competing with Firefox’s built-in one, and having Firebug and HTML Validator enabled for all websites and not just localhost. My current Firefox experience is alarmingly fast and stable—after a couple of tweaks, natch—and once again all is right with the world of open source software.

Another significant change—and one that affects you, the steadfast visitor—is my decision to host this site with my employer and dump the deplorable Dreamhost, who should seriously consider changing their name to Nightmarehost after perpetrating an extended era of ineptitude on their customers, myself included. I certainly notice a dramatic increase in the speed of Bradezone, and hopefully you can too.

UPDATE: My anger was misguided.

The experience of the software developer is a bit more vexatious. The hope is that we (or our IDE) will notice a mistyped letter or slightly flawed logic before we unleash imperfect software on the masses, but unfortunately “bugs” are a fact of life. Witness the number of major companies such as Google, Apple, and Microsoft that release software tagged with the word “beta”—a term that in the world of software programming I would describe as politically correct. It absolves the software provider of responsibility and is roughly an open admission that things might not work as intended.

With computers, everything is black and white, ones and zeroes, pure logic. This fact actually appeals to most programmers and provides us with a constant challenge as we write software. But without shades of grey, we are bound to continue producing otherwise exceptional products that are ever so slightly tainted by the stain of human error. The average citizen has used enough software at this point that they almost expect problems to occur, and as a result software developers are often viewed with some degree of suspicion. What can we do about this problem of error-prone software, and how do we improve? Certainly testing mechanisms are already in place on development platforms, but even then we are limited by our inability to foresee all the possible scenarios that might result in errors. Testing techniques have improved, but so too has the complexity of software skyrocketed, leaving us in roughly the same position.

The harsh reality is that this problem will never disappear completely. I anticipate that significant strides will be made via new automated testing methods, new programming languages, and simply better documentation and training. But as a software developer I know all too well that my mistakes, however scarce, will always be prone to unveiling themselves in a most garish fashion and to my enduring chagrin.

It’s nice to see there are other people who are willing to have a bit of cheeky fun with these random web startups.

I used to be an organization freak who would willingly subscribe to the rigid structure of this semantic web, but over the years my concerns have become far more practical: what can a website do for me today? I don’t care if other (possibly non-existent) applications can “understand” the content on my web page. The amount of work required to make that happen doesn’t match up to the supposed advantages of making it happen. In the end and as usual, the mob and the intelligentsia will have to settle on a compromise—neither a perfectly categorized semantic web nor a hideously broken myspace-esque web are feasible. The solution? I nominate microformats. They are a cinch to incorporate into existing code and once standardized they can be recognized by a bevy of applications. Their website says it best: rather than trying to reinvent the web, they merely “pave the cow paths.”