Had a daydream just before falling asleep last night, in which I was a writer for Lost way back at its conception, and I was fighting the other creative folk for using Charlie's character not to display the evils of addiction with heroin, but with cigarettes! I mean what self respecting heroin junkie wouldn't smoke as well?
I know that I didn't pay enough attention to the first series so I'm unsure if there hasn't been any mention of this, but I sure can't remember if any of the main characters have ever smoked or wanted to smoke. And it just seems unusual to me that out of the number of survivors how this issue hasn't cropped up to be a major story line.
Anyway, this of course led to me thinking up all sorts of funny "Man I need a smoke!" scenes and how it could be yet another resource that Sawyer could control and finally about all the inter-survivor rivalry that would occur between those that were able to give up easily vs those eking out the last of the duty free supplies performing tricks for Sawyer along the way! I think it would have been great.
Anyway, as life continues to imitate art, or at least a major TV series, here is a link to Lost related crime.
--
In other news, my dealings with recruitment agents imitates Sara Lee in a crazy "Layer upon layer, upon layer" farce. One of the jobs I'm applying for goes a little something like this: I'm applying for a position within a company that has outsourced the work to a project management consultancy, and this consultancy needs workers so have advertised through their preferred agency, which in turn put the word out through other agencies. Thus I was alerted to the position through my agency and now I've been interviewed for my agency for the position, and then their agency and yet I still have two more layers to go before I can even work out who the hell it is that I'll actually be working for! It is SUCH a dumb system.
In the meanwhile I am continually yours, unemployed...
--
C++ headaches are becoming the norm. It may also have to do with the amount of caffeine in my system, but I've never been one to blame coffee before so why start now. I managed to spend nearly two hours troubleshooting a programme just because I was too blind and dumb to see that ONE line was missing. I'll tell you now that I'll never make THAT mistake again, but am a bit freaked out that I can be stumped for that long on something as trivial as it ended up being.
Ah well, at least my d6 is now rolling pseudo-random numbers in a way that I can 70% fully understand. I guess that is the problem with me, I'll all like "Yeah OK, this guy here did this to get this to work, but how does it actually work?" and proceed to get bogged down writing a whole lot of extra code to interrogate the solution so that I can try and see what is happening. It is far from efficient, causes headaches, and generally leads to only a 70% understanding before I have to concentrate on something else or go MAD.
--
Finally, I have myself my very own printed copy of RTB. It is printed Two-Up and double sided but unfortunately in booklet form, so by all accounts it is an unusual publication. But it is going to make the reading, and typo identification, run like a fleet footed moose (sans cobbled ankle)!
My second fave typo thus far, pg 105 last paragraph, 'You're a good moth.'
~m I'm only pointing theses out so you don't get a FAT head when I tell you later how much I'm(ve) enjoying(ed) it!
--
Have a good weekend
No comments:
Post a Comment