Most parts of my job entail details. Whether it is writing code correctly or helping a client choose meaningful keywords for them details do matter. As a long time programmer I learned a long time ago that details matter. If you misplace a semicolon in some languages then all sorts of things can go wrong. When someone says that they just changed this one thing (usually in code) and it should not affect anything else, my ears perk up.
Some recent examples of details that were ignored: the dead battery on the emergency cut off valve on the leaking oil well in the Gulf; goals that were missed/wrongly awarded in the world cup; the iphone 4 antenna placement; volcanic ash and airplane interaction. All of these issues has to do with details. Everyone has different skills and one of my skills — I think anyways — is details. Now I cannot spell very well as all my clients can attest to but getting the text into the right place at the right time, I can do that.
Here are a couple of details that I have had recent success with. I have done some research into why certain pages on a clients site were so slow to load. I had to dig into the code — the pages are generated with data from a local database and added into a mashup with google maps — and expose different layers where the slow issues might be found. At the end I found out that I had not added an index to a table in the database. Simple solution and the pages came back to life in the fast lane! That was a tough problem that I need a variety of skills and tools to find the issue. Details.
Another example of details in action was doing an evaluation of a clients site. This became a bit tricky for a variety of issues I will not get into here. The end result was that I was able to find a way by using Google Ads to direct traffic to their site using some keyword phrases that for some reason they were not currently using. Those keywords help to drive traffic up to their site significantly. They already had a click campaign running but — details — they had let this set of keywords phases slip away.
I am a details kind of guy and usually like digging in to figure out what is currently going on. So whether it is in code or evaluation of a site or an issue I like getting down to the details of what is really going on with a process. Sometimes this might take a long time and multiple tries. The issue I spoke about above with the database took me months to really figure out what was going on, the fix took minutes to implement. Your grandmother was right — “The Devil is in the Details!”.
pete reum

