// Commented

#include
using namespace std;

int main()
{


Today I meandered over to the Guildhall, where the Cambridge University Engineering Society today hosted its Annual Careers Fair. An assortment of companies were present, including the likely suspects of BP, Shell & Rolls Royce, as well as others like British Sugar, who apparently don't just do sugar but also tomatoes, and various others who, as is the case with most of these corporate events, are only interesting for the freebies.

My shopping bag today consisted of:

2x highlighter - Faber Maunsell | Aecom, Shell

3x biro pens - Faber Maunsell (again), ARM, British Sugar

1x blue plastic 'Frisbee'/non-aligned flying disk toy you play Ultimate with - Sentec

1x orange foam boomerang - Tandberg. I've given this a try and for the most part it just flies in a vague forward arc with little suggestion of a return path. Might need more space.

1x stress ball in the form of a ripe red tomato - British Sugar

1x blue squidgy foam armchair for the resting of mobile phones - ARM [geddit?]

1x hand-crank dynamo-powered emergency mobile phone charger/torch - ARM. Bearing the cunning text of "ARM-powered". I c wut u did thar.

I also gave this item a trial run, and the torch element wouldn't be something I'd immediately leap for in a crisis. Takes a good deal of gyrating to get a current going, and the bulb promptly cuts out when the crank stops turning. Needs a capacitor mode I reckon.


The image of note from today's post is a screenshot I took of the Faber Maunsell website. Now, being a cautious Firefox user, I browse almost always with the NoScript addon active. This handy little device essentially blocks all JavaScript, flash plug-ins and coding that websites have by default, but informs me of elements that are being blocked, who owns them, and whether I want them on my whitelist or not. Essentially, I don't want my browser to pick me up a keylogger on my travels.

So anyways I take a trip to Faber Maunsell out of common interest and see the crazy text:

// Provide alternate content for browsers that do not support scripting
// or for those that have scripting disabled.

and it made me smile. Having dabbled my hand with C++ these past weeks and following a few years of awareness to the xkcd community, it amused me to see // COMMENTED! lines appearing in a website's final display to the viewer. It also seems like the second line was an after-thought or edit from a second developer. First goes in there, types the code with either normal users or those stuck on Netscape in mind. Second checks it out and adds the third category - overly cautious JavaScript annihilators.

But yeh, // for the win really.


Those concerned about yesterday's musings reading "2nd post in a week" and seeing it paralleled with one listed for 12 days beforehand: here's an explanation. That post was initially drafted a few days after seeing QoS, but it wasn't until last Friday, 14th November, that I finished it off and posted it. Curse ye Blogger and your definition of 'post date'. Those who are seriously pedantic can have the "two posts that went from start to finish in a seven-day timespan" now I suppose.

return 0;
}