TechCast Reviews

The Bates model for IE-fixing

24th May 2009

Share or save this page:
Share/Save/Bookmark

The Bates model first introduced in May 2009 describes, in five discrete stages, a process by which web developer’s deal with grief and tragedy, when confronted with the task of IE-fixing websites for their clients. This article attempts to describe some of the pains that web developers go through to get around the issues and challenges that Microsoft’s Internet Explorer presents.

Denial
Denial is usually only a temporary defence for the developer. Web developers who have spent years honing their skills in writing elegant code are often left in dismay when they load their work in Internet Explorer. Prior to this, and during development, it is likely that the developer has a belief that there is no way that Internet Explorer could interpret the CSS in any other way than what is described in the code.
This feeling is generally replaced with heightened awareness of Cascading Style Sheets (CSS) thanks to the extra work that Internet Explorer introduces – well after a project is considered complete.

Example – “This site isn’t going to need any IE-fixing.”; “This can’t be happening, not to me.”

Anger
Once in the second stage, the individual recognizes that denial cannot continue. Because of anger, the person is very difficult to care for due to misplaced feelings of rage and envy. It is often that the surrounding equipment and objects on the desk experience the full brunt of this rage. This usually results in the destruction of keyboards, LCD monitors or excessive cursing at the company that is responsible for Internet Explorer.

Example – “Why me? It’s not fair!”; “How can this happen to me?”; “Why did they dismantle the IE development team after version 6 was released?”

Bargaining
The third stage involves the hope that the developer can somehow postpone or delay fixing the IE problems. Usually, the negotiation is made with the client in exchange for a quicker turnaround time. Psychologically, the person is saying, “I understand the problem, but give it time and people will eventually abandon the use of Internet Explorer…”

Example – “I promise I’ll give my iPod to charity if people will stop using Internet Explorer.”

Depression
During the fourth stage, the developer begins to understand the certainty of requiring an IE fix. Because of this, the individual may become silent, refuse visitors and spend much of the time crying and grieving. This process allows the developer to disconnect themself from things of love and affection. It is not recommended to attempt to cheer an individual up that is in this stage. It is an important time for grieving that must be processed.

Example – “I’m so sad, why bother with anything?”; “I have to do this with every project. . . What’s the point?”; “I can’t take this pain anymore, why go on?”

Acceptance
This final stage comes with peace and understanding of the IE-fixing that is approaching. Generally, the person in the fifth stage will want to be left alone. Additionally, feelings and physical pain may be non-existent. This stage has also been described as the end of the dying struggle.

Example – “It’s going to be okay.”; “I can’t fight it, I may as well prepare for it.”

Note: Adapted from Wikipedia. Kübler-Ross model. http://en.wikipedia.org/wiki/K%C3%BCbler-Ross_model. Accessed on 24/05/09.