IE6-It won’t go quietly

As I mentioned in a previous post, Microsoft has now begun a serious effort to kill off Internet Explorer 6.  No issues there, this elderly (+10 years) browser is not secure, and comes nowhere near supporting modern standards.

About 3 weeks ago, Microsoft announced that they would start updating old browsers as part of silent automatic update vice Windows Update.  Many Windows users understand the difference, for Windows Update a small balloon appears in the bottom of the screen announcing that updates are available.  The User must agree to take the update, and many people just don’t want to be bothered, so they ignore the advisory or close it.  This is where Microsoft traditionally put the browser updates, which makes it one of the reasons that there are so many vintage versions of IE out there.  With Automatic Update, for most systems when the User shuts down an alert appears that says “do not turn off your computer, installing update 1 of 14″ or some such.  Bottom line, with Automatic Update, you are “accepting” all of the updates Microsoft is giving you, and they don’t tell you what those updates are.  That said, I like Automatic Update, and heartily endorse it for all Windows users.  Automatic Update is where you get the security updates that help keep your system safe.  If you are running Windows without it today, thrust me, you NEED to turn it on.

So, back to our saga, Microsoft will start including a browser update in Automatic Update.  If you have XP, you will get IE8, if you have Vista or Windows 7, you’ll get IE9.   You’ll turn your computer off one night, the next day you have a new browser.  This will certainly drive down usage of IE6 at high speed, maybe even eliminate it in some areas.   Hooray!  Web Developers everywhere are calling it the greatest thing since we learned Godzilla could fly.  No longer will we have to support IE6!  Huzzah! (Huzzah?)

As a user of IE, you might not have the same perspective.

Firefox and Chrome users are used to getting forced updates periodically, it’s just part of the experience.  The difference is, these smaller upgrades make change happen gradually.  Users barely notice it the difference in their Chrome/Firefox browsers.  Not so with the IE change, now we’re potentially talking about turning off an XP system running IE6 one night, and coming back to IE8 the next day, an upgrade of two full versions.  While Microsoft assures us that Preferences will be preserved, that’s only part of the package.  What about all of those toolbars that made browsing easier?  Gone.  Helper objects?  Gone.    The User will barely know what they are looking at, let alone know how to get anything done.  It’s going to be brutal.  The User will not be happy.

But wait.  Microsoft has an answer for this also.  The rollout will be gradual, and will start in Brazil and Australia.  Great idea, do it first in two backward third-world countries populated by savages, far enough away from Redmond they probably can’t go there in large numbers and start burning down buildings.

Um, Third World?  Savages?  Turns out that there are 194 million people in Brazil.  According to internetworldstats.com, about 67 million use the Internet. Seems those Savages are rather well hooked up.  The fascinating site ie6countdown.com claims that usage of IE6 is around 1.4% in Brazil, so that gets us roughly 94,000 people who are going to get converted from IE6.  For Australia we’ve got 17 million Internet Users, with IE6 usage also at 1.4%.  So about 23,000 people will suddenly make the switch.

Gosh Steve, that’s only about 110,000 people, give or take, who will go through this agony, not a lot in Internet terms.  But what if all of them call YOUR Tech Support line at the same time?  And this is, after all,only the beginning.  We’ve got a few more countries to go.

Bottom line, while I support the effort to eliminate IE6, I think the guys in Redmond will need to do more thinking about this.  It’s not going to go well.  Not like this.

Posted in Uncategorized | Leave a comment

Internet Explorer 6, Not Really Dead Yet

A few days ago, the folk at Microsoft baked a really nice looking cake (pictures are all over the Web) celebrating the “death” of Internet Explorer 6.  “Death” in this case means estimated usage in the United States has dropped below 1%.  Any way you look at it, this is a good thing, developers like me have spent a lot of time supporting IE6 as the standards for web development move way past it’s capabilities.  IE6 was first released 27 August 2001.  Ten years is a long time for software like this.  So good riddance.

Unfortunately, this good news announcement may be a bit premature.  This 1% is still a lot of people, many of those apparently corporate users tied to old network structures.  Real customers, not Earl and Ma out on the farm.  And IE6 still has over 25% of the base in the People’s Republic of China.  Whether or not these are legitimate copies of IE running on legitimate copies of Windows, we’re talking about the largest emerging consumer market ever.  IE6 is not dead enough yet.

The only way to really eradicate this kind of pest is through a concerted team effort.  As an Open Source LAMP developer, my relationship with Microsoft has been spotty in the past.  This time I’m getting on board.  I have added code to my home page at http://www.sitetuneups.com that advises Visitors if they are running IE6 and offers an upgrade link.  You won’t see it if you are running a current browser.  I’m also officially ending my support for IE6.  I will not include such support in any contract.  The trash-burner Dell CPU I have kept all these years for IE6 testing will be re-purposed or sent to it’s final resting place.  Over.  Done.  Goodbye IE6.  I’m out.

If you have a website and you want to join this drive, you can copy the code from the IE6 Countdown Website and add it to yours.  If you need help installing the code, contact me through the Site Tuneups web site, I’ll do what I can to help.  Let’s try to push the 1% to zero.

Posted in Uncategorized | Leave a comment

A Basic Step by Step Guide to Getting Results from Technical Support

I usually provide quite a bit of technical support during a website development.  Even after the job is done, I try to be responsive to former Clients (your best source of New Clients).  Since most of my clients are also in San Diego, the call is cheap,and it is nice to stay in touch.

Often I can’t really help, especially if a Client is having a problem with a service provider, such as their web host or Internet Access Provider.  Most people do not understand that these providers by and large will not talk to me, for the very real reason that I might be a hacker trying to hijack a website.  So I tell them that they are on their own, and give some basic advice.  Typically, a long silence ensues.  I know that they would rather have their teeth pulled out by clumsy robots than call Tech Support.

So I say something encouraging “Come on, you can do this” and they come right back with “Easy for YOU to say, you are a techie like them”.  While that might be true, it isn’t really relevant.  I think anyone can get results from Tech Support, and I think the vast majority of Tech Support people earnestly start every day intending to provide quality service to people who are not Techies.  So here is my Guide to having a quality experience when contacting Tech Support.  Note that a lot of these steps are taken BEFORE contacting Tech Support.  If you really think you “don’t have time for this” then you are in for a life of technical disappointment.  So read on….

BEFORE you call Tech Support, follow these steps:

  1. Can you duplicate the error?  By that I mean, can you document a set of steps that will produce the same error every time?  Write those steps down.  The first thing  you tell the technician after a brief description of the problem is “I can duplicate this error, here are the steps”.
  2. Record EXACTLY any error messages you receive, including any obscure looking error code numbers.  If you can, copy the complete error message and paste it into NotePad or similar, or take a screen grab if you cannot do anything else.
  3. Do what you can to help yourself.  Look on your Provider’s website for a FAQ (Frequently Asked Questions) or some sort of knowledge base.  Run a Google search on the exact error you are receiving.  Sorry, but no matter what it is, you probably are not the first person to have this issue.  If something looks good to you, and you try the proposed “fix” be sure to document what you did, and what the results were, such as is there a new error, or is the system behaving differently, but still not performing.
  4. Look up any pertinant access passwords.  If you are having problems with email, have the passwords for ALL of your mailboxes available.  Similarly, look up any account numbers relevant to this provider.
  5. If you talked to another professional, and took some/all of their advice, document what you/they did.

NOW, armed with your documentation, you are ready to contact Tech Support.  The questions becomes “How”?  Many providers offer a choice of email, chat or telephone.  There may also be a formal trouble ticket system.  For myself, when a trouble ticket system exists, I use it, even when I am in a hurry, especially if I don’t think Tier 1 Support can solve it (more on this later in this post).  Often my issue gets kicked upstairs and solved in a few hours with just the one submission.  So it actually saves me time.  My second choice is chat, because the Technician’s instructions appear in front of me on the screen, and I don’t have to ask the Tech to repeat something.  My last choice is the telephone, unless it is something really minor, and I’m pretty sure I won’t get put on hold.  Use what works best for you.

So you have made your choice for a contact method, BEFORE YOU START, understand who you will be dealing with.  A bit ago I referred to Tier One Tech Support, the person who first picks up the telephone, or answers Chat, or deals with the email/ticket queue.  With minimal training, and usually a pretty good tech support database system on the screen in front of them, these worthy people can help with issues on the Client’s computer such as email access, password recovery, virus sweeps of a website, that sort of thing.  These folk probably solve 80% of all issues, and chances are one of them can solve yours, so don’t try and intimidate your Tech into sending you to someone “who knows what they are doing”.  Their performance is graded on how many issues they can solve, as well as how many calls they let through to Tier Two Support that could have been solved at the Tier One level.  Tier Two support costs your Provider a LOT more money to maintain.  For an Internet Service Provider (ISP) these Tier Two individuals are usually Junior to Mid-Level Systems Administrators with the power to make configuration changes and the like.  They don’t work cheap.  As an individual, it is unlikely that you will ever deal with Tier Three, unless you yourself are the Administrator for a dedicated system that your Provider is maintaining or similar.  Now, guess who makes the decision that your problem is worth sending to Tier Two?  That’s right, The Tier One guy you want to ‘diss.  So calm down, use your indoor voice, and make the contact.

Now on to that final step, and I’ll bet you know this is coming….try to leave all of your various frustrations out of this.  Describe your problem, detail the steps needed to duplicate it and explain what you have done so far without questioning the Tech’s parentage or the honesty of his/her company.  You will get real respect for your professional approach and the fact that you are trying to help yourself.  Do what you are asked to do, even if your Tech sounds like they are perhaps 12 years old.  Chances are you will be pleasantly surprised at this person’s personal commitment to solving your problem, and even happier with the end result.  If you don’t get what you want on the first try, be polite, but persistant.

And yes, even though I am a “techie”, this is exactly what I do.  Good Luck.

Posted in Uncategorized | Leave a comment

The Free Lunch Was Never Free, Neither is the Free Website

I was working through a keyword strategy the other day, using one of the available tools, and was struck by the number of searches done with the phrase free website.  It was very substantial, leading me to believe that there was (and is) considerable interest in obtaining one.

You have to admire that optimism, at least at some level.

There is an old saying that pre-dates me, “The free lunch was never free, someone paid for it”.  Any time you get something for free, the entity that actually paid for it would like something in return.  Sometimes that something is just your continuing attention.  One of the smartest online marketers ever, Seth Godin, built an entire successful strategy around the idea called Permission Marketing.

I’m out in the Community quite a bit flogging my services as a web developer, and I have to admit I get quite  a few inquiries along those lines.  I’m serious, I literally get asked, “how can I get a free web site”?  Usually I tell them, and here is the thing; it takes work, usually a lot of work.  Whether you go with WordPress or other blog software, use a Site Builder provided by an ISP (Like Website Tonight, offered by GoDaddy), or go with a shareware template,  you will put a lot of time into this site, and frankly, your expectations better be modest, it won’t look like Amazon.com when you are done.  So somebody paid for that free website, and that someone is you.  I once heard a very smart man (I think he wants to remain anonymous, don’t you Neil?) make this pronouncement at a panel discussion “The only thing you really have to sell is your time”.  Your free website wound up costing you quite a bit.

So what to do?  My advice, if you are just starting out, in many markets you can go with a home-built blog or a Site Builder, but be realistic about what you will get for the time you spend.  In short, throw something up behind your new domain name that is not horrible in appearance, and very accurate in content.   Don’t let anyone tell you that your site will get ignored by search engines, my mechanic built his own site with an ISP-supplied  Site Builder.  When you type his top keyword phrase into Google, he comes up number two, between two giants in the industry.

So keep your first site simple and your expectations modest.  When you finally outgrow your starter site and need more, there is a starving developer who would like a word with you….

Posted in Web Design and Programming | Leave a comment

Website tag management, good solution to an old problem

Last week I went to a lecture/luncheon sponsored by the San Diego Chapter of the American Marketing Association.  The Doubletree put out a fine Cobb salad, and Jesse Nichols of Google Analytics put out a fine lecture.  At the end of the lecture I asked Jesse if Google had any plans to automate page tagging.  It was clearly a question he’d heard before (a lot) and he had a good solid answer; No.  He cited liability issues and the like, but the fact is it’s just not a place where Google wants to be involved.

What am I talking about?

If you have ever set up a Google Analytics account, you know about this one.  Setting up the account is fast and easy, and you log out with visions of fascinating reports soon to come.  A week later you find out nothing is happening.  That’s when you do some poking around in your Analytics account and discover that the pages need to be “tagged”.  The tag is easy enough to get, you push the right button in your Analytics account, and Google gives it to you.  Now you just need to copy it out and paste it in to your web site pages.

Paste…..in.  What?  How?

Google is helpful about this “before your closing head tag, which looks like this </head>”.  Super.  You are pretty sure that this exercise even if you had some way of doing it will result in the destruction of your entire site.

That’s how somebody like me winds up plodding through your web site, inserting the tag, deleting previous versions of the same tag (really common to find a couple of those) and cleaning up the code.  I get paid, can’t argue with that, but it’s right up there with pulling weeds in the excitement category.

There is another answer.  A San Diego company called Tealium now offers Tealium IQ tag management software.  From one console, you can manage your various analytics tags (you do get three different reports, don’t you?), affiliate tags, advertising tags, etc.  Tealium does not do pricing on their website, so you can bet its not all that cheap, but if your website has multiple tags, and you pay a Developer to manage them, you might want to sit down and do some ROI math.

I’d love it if Tealium would  offer a freeware version that just managed a tag or two.  Every Mom and Pop web site on the planet needs it  Just a thought.

 

Posted in Web Design and Programming | Leave a comment

The Google Panda Update Can Affect You Too

If you have not heard of the Google Panda update (some call it Farmer) you may have seen its effect.  Google rolled out Panda early this year, and the impact on search results was nearly immediate.  Unlike many Google updates, Panda is really a filter, that is, it filters data that Googlebot has already indexed.

Panda went after low-quality web pages.  Anyone who does a significant number of searches has seen these, the search result looks perfect, but when opened it gives up little gifts like “how to repair a watch band is a really good idea”.  Sometimes the content is auto-generated, sometimes it is simply copied (scraped) from legitimate sites.  Either way, the Visitor is usually left wondering “why did I bother to click on that”? Generating low-quality high keyword content pages had become somewhat of an art form when Google decided to take action.

In a very short period many high-ranking sites dropped far back in Google search results for targeted phrases.   For the owners of these sites it was a disaster.  Even months later many are struggling to recover, and they will probably never recover their investment in thousands of pages of fluff.

My point is that there is an opportunity here for many.  For site owners who never understood why their competitors got higher rankings, even thought they “did everything right” until they finally gave up trying, it might be that the playing field has been leveled.  Which means it is time to give the site a fresh look, perhaps tweaking the messaging and re-writing old pages,  making very sure that none of those pages got tagged as low-value content and improving the quality if they did.  It may work, it may not, in my mind it is worth the effort, and now is the time.

Posted in Web Design and Programming | Leave a comment

Why Are All of the Websites So Small Now?

So, you’ve noticed lately that all of your favorite websites are now all scrunched up in the middle of your screen.  What happened?  I’m guessing you just got a new monitor, right?  And the only thing you could buy was one of those really wide ones?  Could be your issue.

Under intense pressure from the Movie Industry, just about all of the monitor manufacturers have begun manufacturing screens with a 16:9 aspect ratio to accomodate HD movies.  “Aspect Ratio” in this case refers to the width of the screen divided bythe height, usually expressed as an unresolved fraction.  So, most of our monitors used to have a ratio of 4:3, almost square.  At 16:9 they are much wider than they are tall.

But that’s not really our issue right now.  Our main concern is monitor resolution, i.e. how many pixels wide and how many pixels across the screen is.  Many of us went from an average width of about 1024 pixels width to around 1920 pixels width.

How does that affect a website? Most modern websites are designed to a fixed width, the most popular being a little under 1000 pixels across (let’s address so-called “liquid sites” at another date).  A website designed to this standard will take up 1000 pixels across, no matter what monitor it is on.  So, when you go from displaying the site on a monitor with horizontal resolution of 1024 to a monitor that offers 1920, the website will take up less of the total screen, and look smaller.

What to do?  Here are a couple of ideas:

  • Get used to using the equipment, after awhile you will remember that you can have your browser open on just a corner of the screen, your email on another, a document on another.  You could learn to love it.
  • Many browsers now come with a zoom capability, which is so much more useful that the traditional utility that just changed the font size and totally messed up the layout.  Look around for it and give it a try.  You might be ok with it, but understand that low-quality images might look a bit grainy when zoomed.
  • Change the resolution of your monitor.  This will make everything larger.  Not really recommended, but you could do it.  See your manual (you kept that, right?)

It will be awhile before all of the old monitors go away, and designers/developers have a habit of designing to the lowest common denominator, so we are probably stuck with 1,ooo pixel resolution web sites for a little while at least.

Posted in Web Design and Programming | Leave a comment

Why Website Projects Fail; the Noah’s Ark Parable

In my profession, you listen to a lot of terrible stories about web development projects gone wrong.  My usual observation after another sad tale is “Well, I’m sure you explained it, and I’m sure the Developers thought they heard it, but somewhere in the middle there it didn’t happen”  This I know is obscure at best, so today I thought I would try to explain myself, using the story of Noah’s Ark as a vehicle.

To avoid a heavy religious reference, let’s refer to Noah as “Noah” and the other party as “Client”.  Right away this project has problems no one appreciates, as the Client jumps right in to the design phase, telling Noah how big the ark would be, what it would look like, and who/what would be going on board.  Noah really wants the contract, and goes right in to build without finishing the design. Skipping fact-finding and performance specification left several openings for mis-understanding, such as:

  • Client didn’t have any idea if Noah actually knew what an Ark was in the first place.  Noah was cooperative because he wanted the work, not because he knew what was going on.
  • Since Client assumed that Noah knew what an Ark was, Client also assumed that Noah knew that the ark had to FLOAT
  • Client never took the opportunity to tell Noah that the schedule for the delivery was ship in place, with an epic flood on the Calendar.  Had Noah known this, he MIGHT have asked the right questions.

We can’t lay this all on Client.  Noah was afraid of losing the work by looking dumb in front of a potential Client, so he went along hoping he would figure out what an ark was during the project.  He never asked any questions, never completed the design, just went right to build.

Thus we come to the epic cartoon, with the rain starting to fall, Noah outside the ark looking up at the sky, and a voice coming down “Whattaya MEAN you need to write a change order?  How could you NOT KNOW it was supposed to FLOAT”?

Just because they say they understand doesn’t mean they do.  Always explain your need in as much detail as you can manage IN WRITING.  Get a response in writing.  Then talk about it.  A lot.  Until the real understanding happens.  Then you are ready to design.  Good Luck

Posted in Web Design and Programming | Leave a comment

“i need a website” becomes “i need a web app”

I saw a great Seminar last week, sponsored by San Diego Ad Club.  Developer Jake Fields held forth on building web applications.  Jake did a great job of defining native apps, written in compiled languages such as Objective C or C++ and running directly on the mobile device’s operating system, web apps, basically web pages targeted to mobile devices, and hybrids, a combination of both.  He also talked about getting started and marketing the resulting products.  It was a well-rounded presentation.  There was one question I wish he had not answered, and it was mine.  In response to the ever popular “how much and how long for this?”, Jake told the crowd that they were looking at 3 months and $10,000.  In fairness, he went on to say that apps like the one Nike recently introduced probably went for over $1,000,000, but I know from my experience that what they heard was “I can get an app like Nike’s for $10,000 in under 90 days”!  Ouch.  Ouch, ouch ouch.  Nike probably spent twice that much time just figuring out what they wanted for basic performance to satisfy a set of goals they already had established.  Jake was right to answer the way he did, NOBODY wants to hear “Oh, it depends” and I’m certain that he has delivered at that price and in that time frame.  But I’m guessing that the Client already had a clean set of requirements and realistic expectations when the clock started.

Posted in Web Design and Programming | Leave a comment

Cascading Style Sheets (CSS) Defined

If you have been involved with a website development in the last five years, you have probably heard of CSS, and you probably know that it has something to do with how the web site appears in your browser.  That’s true, and much more.  CSS allows us to manipulate where text appears on the page, as well as how it looks.  We can create complex navigation schemes with drop-down menus entirely in CSS (with just a bit o’ Javascript to take care of some browsers). In fact, we can remove the presentation entirely from the content, so that all you see on an HTML web page is, well, HTML (and Javascript if the page has any).  Why do we want to do this?  A really good reason is so we can have different style sheets for different user-agents (browsers, handhelds, printers etc.).  The HTML can be presented differently depending on the device.  We can even use CSS to hide elements from a device when the device can’t display them.

To really understand how this works, I can’t think of a better place to go than the CSS Zen Garden.  This website, launched quite  a few years ago now by leading CSS and HTML gurus, is an ongoing project for showcasing design using CSS.  Basically, the HTML for every project is the same. The submitting artist can only supply CSS and supporting background images.  Think it’s impossible to design like this?  Check it out:

http://www.csszengarden.com/

Be sure to click the links in the sidebar to see some of the recent designs.  You’ll see the text is the same for each design (you sometimes have to really look to find a particular piece of text).

Enjoy!

Posted in Web Design and Programming | Leave a comment