Posts Tagged ‘unnecessary’

A case study: Why “meeting for meeting’s sake” is bad

Monday, February 1st, 2010

source: mitopencourseware / flickr

We all know meetings are bad (if you don’t, then you’re in the wrong place). But “meeting for meeting’s sake”, a repeating meeting that occurs regardless of an agenda or need, is not only really bad, but potentially destructive.

This is the story of one such meeting. The meeting was a monthly meeting with only a vague description. This instance of the meeting had no agenda until just 30 minutes prior to the meeting’s start. Nobody came prepared, nor did anybody know what to expect. On top of that, important participants were missing, as they were in another meeting.

In my mind, this was a meeting that had every reason to be postponed, if not completely canceled. Unfortunately, the decision was made to hold the meeting anyway.

The topic was controversial. Being that there was only a 30 minute lead time on what the meeting was going to be about, those opposed to the topic had absolutely no time to formulate a response and alternative solution. Those in favor had no idea of the opposition they were about to face.

The conference room was a tinderbox; emotions got heated very quickly. Those opposed reacted from pure gut instinct because they did not have solid facts to work with and had to reach for arguments against. Those in favor reacted emotionally, also due to the lack of preparation, as they were unaware of the hastily arranged, albeit unintentional, ambush awaiting them.

The meeting ended slightly prematurely, with all sides leaving angry. This meeting did more damage than anything else.

What should have happened? There were two major, if not fatal, mistakes made. First, the meeting should have never occurred because there were people who needed to be there who were double-scheduled, and had to go to another meeting. Those people had important information that could have made the meeting go smoother. Secondly, there should have been an agenda for the meeting published several days ahead of time. This would have allowed the opposition to come up with fact-based arguments and an alternative solution, as well as given the proponents time to realize there was an opposition, and to make preparations for that.

When you find yourself scheduled to attend a ‘meeting for meeting’s sake’, don’t just think that you’ll be wasting time. You could be damaging workplace relationships and putting your projects in peril.

You forgot to include kitchensink.com

Tuesday, December 1st, 2009

Sometimes strange things catch my attention. As a web professional, sometimes web sites acting strangely catch my attention.  Over the last couple of days, two different sites did things that not only caught my attention, but completely blew my mind. And not in the good way.

One of the sites (which will remain nameless) is a tech blog I normally read via RSS, but I found myself actually reading from the site recently.  As I did, I noticed the status bar flickering, and the load progress bar not quite all the way to the end.  The page was obviously still loading, but it appeared that the page was complete.  As I scrolled down the page, I noticed that the blogroll used the favicon of each blog listed in a very long list.  Because I do not visit many of the sites on that blogroll (apparently), my browser had to go to each site and download the favicon for each blog. The good news about that is now that I’ve fully downloaded the page, I have all those favicons cached, and subsequent loads of that page should be snappy, but I have to wonder if there isn’t a better way to do that.

It could be possible to put all the favicons into a sprite image, and download the single image file and let the browser’s CSS do it’s magic.  However, there are (at least) two things wrong with doing that.  First, if the blog’s owner decides to change the favicon, the incorrect icon will appear in the blogroll until the sprite image is updated. Second, copying somebody else’s graphic handiwork onto your server is ethically shady. Ethically, the blog’s designer did the right thing and reference the favicon from each of the remote sites. Unfortunately, the ethical thing to do was not the speediest thing to do. In this case, the blog’s designer would have to ask the question “does including the favicon from each of these remote blogs add any value worth the hit in performance?”  In my mind, the answer would probably be no.too-many-includes

The first attention-grabbing site was a personal blog site.  The second, however, is a high-traffic tech news site (which will also remain unnamed). This site is big into embedding JavaScript or Flash from other sites on their page.  The reason I know this is because I use a Firefox extension called No Script that blocks all JavaScript and Flash content unless I have explicitly allow a given hostname.  The image to the right is the No Script status bar. Note the number of sites. That’s a lot. (An aside: The sites with the blue S icon are those that I have not allowed to load, and the sites with the red circle and slash through them are being allowed.) Many of the includes are for site tracking or commenting, but in my mind, there are way too many includes here.  All of these things take time to load.  This, too, would be another one of those situations where the site’s designer has to ask if the value added by all these includes is worth the extra time it takes to load the site.

This same site doesn’t come close to having well-formed HTML, either.  Below is the output of HTML Validator, showing not just a large number of errors, but several frames as well.  I had thought frames died in 1999. Apparently not.

too-many-errors

Unnecessary Inventions, part CCLXXIV

Thursday, November 5th, 2009

Today, Twitter co-creator Jack Dorsey announced the Next New Greatest Thing: the ability to pay for things using your iPhone.

Well, that’s not so new. That’s been going on in Finland (home to Nokia) for quite some time now.

But, unlike those earlier attempts, this Next New Greatest Thing actually has an add-on to the iPhone to make payments. It’s really a shame (Bluetooth) that there wasn’t something (wi-fi) that came with the phone (3G) that could communicate with a vending machine (SMS) without an add-on.