# Styling With EM
#### Standards HTML XHTML CSS DOM #### Extras Tools Reviews Commentary Weblog #### Basic Contact Home | ## On Being a Web Mechanic Once upon a time-- okay, it was last Thursday-- I went out to my car and discovered that it wouldn't start. The dashboard clock was dead, so I knew there was absolutely no power available. Now, another man might have tried jump-starting the car, or maybe rolling it forward to pop the clutch, or something similarly manly. I called AAA; that's what I pay them for, after all. A guy came out and gave me a jump-start, and the car seemed fine. He left, and I let the car run for about twenty minutes to charge the battery. Then I went about my day. The next morning, the car had flatlined again. I called again, and they sent someone else. This new guy looked at the engine for about a minute, and then he said, and I quote, "Ah!" He reached in, fiddled with something, and then told me to try it again. Bingo. I asked him what the problem was, and he told me that a battery cable had been loose. Tightening the connection fixed the problem. It was that simple. So what's the point? If I'd known something about how the engine works, I could have fixed the problem myself, thus saving myself some expense and several other people some time and effort which could have been devoted to better things. Sadly, all I know about cars is the interface, and how to make them go where I want to go. In this sense, I'm pretty much like Web designers who spend all their time in a visual editor like Dreamweaver or GoLive, and don't know the first thing about deciphering the program's output. Is that bad? Depends on how you look at it. After all, should I have to understand how the engine works in order to drive a car? Of course not! Nearly a century of progress in automotive design has resulted in a set of standards (local ones) on the operation of cars. If you've driven one American car, for example, you can almost guarantee that you can drive any other car. And filling the tank is similarly simple, since they all have the same input mechanism there too. Of course, the Web hasn't had a century to shake out the kinks. At this point, every Web designer either has to be a code mechanic, or else know one, because inevitably they're going to come up against an inconsistency between browsers, and that visual editor isn't going to help decipher the problem. Someone will have to pop the hood and tinker with the engine in order to get it running smoothly. So when people ask me why I stick with my trusty copy of BBEdit instead of picking up the latest visual editor, I tell them: if I'm going to live and die based on how well my pages do, I'd better damned well know exactly how they're created, and why they end up as they do. I had to put in a lot of time learning the ropes, but believe me when I say that's more than paid off in the consultant fees I would have had to pay if I didn't know how to do my own engine work.