We’ve all had the moment when we search for an answer to a technical question and our search engine suggests a trip to ExpertSexchange.com. Er, ExpertsExchange.com. And when we realize that they expect us to pay to see the answer, our instincts take over- we scrub our way through the page source hoping to see a way around the paywall.

If your question was, “Who do I blame?”, that’s one answer ExpertsExchange will give you for free.

// Blame Peter
           // Temporary BTF hacks pending #9888, #11523.
           // Temporary BTF-Related Popup hacks pending #11541, #8286.

           // This is necessary until a global popup solution (#8286) can place all popups in the body, 
           //for proper positioning above all content.
           // This would be relatively simple to acheive (move popups to <body> after DOM load) 
           //but there are async requirements for file upload that force parent component dependencies. Lame-sauce

On the other hand, there’s no evidence that Peter is to blame for this WTF also hidden in their code:

var s = setUpOmnitureVariable('eexchangeprod');
     s.pageName="LO - 20120315-EE-VQP-007"


     s.eVar49="B - 500"
     /************* DO NOT ALTER ANYTHING BELOW THIS LINE ! **************/
     var s_code=s.t();if(s_code)document.write(s_code)//
[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!