Tuesday, July 6, 2010

Two Five

It's official - despite my best efforts to slow down time, my birthday has come and gone and I now have to face the fact that, yes, I am 25.  TWENTY FIVE.  That's 0.25 centuries.  That's 2.5 decades.  That's 1,304.4375 weeks.  That's 9,131.0625 days.  That's 219,145.5 hours.  That's 13,148,730 minutes.  That's 788,923,800 seconds.  That's 788,923,800,000 milliseconds.  That's 788,923,800,000,000,000 nanoseconds.

In other words...I'm old!  I'm entering a new era in my life and it's time I take a look at my life from a different perspective.  So in honor of entering a new age bracket and new perspectives, I've decided to start a new project.  My last project was to do 30 New Things in 30 Days last September so for this new project I'm going to try and take a photo a day for an entire year, with the hope that each photo will show something from a new perspective.  Or at least maybe something that you haven't seen before.  It's a big challenge, and I'm not sure if I'll be able to complete it, but it's worth a shot.  Just keep in mind that I'm a total amateur when it comes to taking photos and I'm using a low end point-and-shoot camera.  I haven't decided if I'm going to upload the pics onto the blog, or just make a Flickr account, but when I figure it out, I'll post it here.


Tune in tomorrow - same Bat-time, same Bat-channel!

Thursday, July 1, 2010

So Long, and Thanks for the Fish

June 30th, 2010...a date that will live in infamy.  Okay, not really infamy, but it'll definitely be a date to remember.  June 30th was my last day as an employee of Dvax, after an amazing run of 2 years and 9 months.  They say you always remember your first - whether it was good or bad, it's forever imprinted in your memories as the first time you've ever experienced something so new and so exciting.

Dynavax represents a lot of firsts for me.  My first real job, my first full-time salary position, my first industry experience, my first cubicle(!!), my first promotion, etc.  But what stands out the most, the most prominent and cherished memories during my stay at Dvax, will always be the people. My crew. My friends. My family.

I was fortunate enough to be a part of something amazing.  It was a smörgåsbord of personalities and emotions:  1 part love, 1 part mayhem, a generous helping of laughter, a pinch of cattiness, topped with a dash of sexual innuendos.  My coworkers made work fun, and I don't think I'll ever meet another group of people like them.  There's not much else to say except...


Thursday, April 15, 2010

I.Am.Nerd.

So I was browsing Xkcd and I stumbled upon one cartoon that I thought was pretty interesting.  Being a nerd, I instantly hit up the search function on Wikipedia to see just what the cartoon was all about.  Why will my friends stop calling me to hang out?  Being a scientist, it's in my very nature to instantly want to do an experiment.

The conjecture states: Take any natural number n. If n is even, divide it by 2 to get n / 2, if n is odd multiply it by 3 and add 1 to obtain 3n + 1. Repeat the process indefinitely. No matter what number you start with, you will always eventually reach 1.

I decided to start out simple.  For my first experiment, I chose the number 11.

n = 11.  Step 1: (11x3) + 1 = 34.  Step 2: 34/2 = 17.  Step 3: (17x3) + 1 = 52.  Step 4: 52/2 = 26.  Step 5: 26/2 = 13.  Step 6: (13x3) + 1 = 40.  Step 7: 40/2 = 20.  Step 8:  20/2 = 10.  Step 9: 10/2 = 5.  Step 10: (5x3) + 1 = 16.  Step 11: 16/2 = 8.  Step 12: 8/2 = 4.  Step 13: 4/2 = 2.  Step 14: 2/2 = 1

Experiment 1 - Successful in 14 steps.

For my second experiment, I chose to use a bigger number: 256.

n = 256.  Step 1:  256/2 = 128.  Step 2:  128/2 = 64.  Step 3: 64/2 = 32.  Step 4: 32/2 = 16.  Step 5: 16/2 = 8.  Step 6:  8/2 = 4.  Step 7: 4/2 = 2.  Step 8: 2/2 = 1.

Experiment 2 - Successful in 8 steps.

Holy crap, I'm on a roll!  And there's a correlation between a larger n and fewer steps to get to 1.  One more experiment and I'll be able to publish my results!

For my third experiment, I decided to choose an even bigger number (they always say: go big or go home!). This time I chose: 123,456,789.

n = 123,456,789.  Step 1: (123,456,789x3) + 1 = 370,370,368.  Step 2: 370,370,368/2 = 185,185,184.  Step 3: 185,185,184/2 = 92,592,592.  Step 4: 92,592,592/2 = 46,296,296.  Step 5: 46,296,296/2 = 23,148,148.  Step 6: 23,148,148/2 = 11,574,074.  Step 7: 11,574,074/2 = 5,787,037.  Step 8: (5,787,037x3) + 1 = 17,361,112.  SHIT.  **Fast Forward**  Step 63: (16,313x3) + 1 = 48,940.   **Fast Forward**   Step 102: (395x3) + 1 = 1,186.  **Fast Forward**  Step 143: (3,077x3) + 1 = 9,232.  **Fast Forward**  Step 177: 2/2 = 1.

Experiment 3 - Successful in 177 steps.

Experimental conclusions:  1) Conjecture stands true...so far. 2) Correlation does not equal causation! 3) I.Am.Nerd.

Friday, April 9, 2010

Cooking Disaster

Gordon Ramsey himself would be proud of my culinary accomplishments of the other night, and by accomplishments, I mean epic failure.  I can cook, I swear I can!  This just happened to be one of my brain fart moments where everything just went to hell.  So without further ado, I give you my recipe for a true cooking disaster.

Ingredients:
1 packet Trader Joe's pre-cut pre-washed Blue Mountain green beans
1 box Trader Joe's Indian Pav Bhaji
1 moment of a lapse of common sense.

Instructions:
Step 1.  Cook rice in a pot instead of a rice cooker.  Watch as it bubbles under the lid and the rice-goo overflows and drips down the sides of the pot.  Watch as this then puddles in the drip pan under the electric burner.

Step 2.  Turn up the heat on said electric burner (complete with dried rice-goo) and watch as said dried rice-goo burns and starts smoking.  Burn and overcook the rice.

Step 3.  Heat up the Pav Bhaji by boiling the sealed packet in water.

Step 4.  Place microwave ready package of green beans into the microwave and heat for 3-4 minutes (according to the package).  Assume that the green beans are fully cooked.  Do not test.

Step 5.  Plate out overcooked rice and pile undercooked green beans on top.  Dish out piping hot Pav Bhaji on top of both the rice and the green beans.

Step 6.  Taste.  Curse.  Smack forehead for own stupidity.  

Step 7.  Take a pair of tongs and try to manually scrape off the Pav Bhaji off each individual green bean onto the rice so that the raw green beans can be cooked properly in a frying pan.

Step 8.  Sauté the green beans long enough so that they're edible but also so that when they're done, the rice and Pav Bhaji are cold.

Step 9.  Place cold rice and Pav Bhaji clusterf*ck into the microwave and heat.  Burn Pav Bhaji.

Step 10.  Epic failure complete.

[Ingredient]

[Step 7]

[Step 9]

Thursday, April 8, 2010

Short Films pt 2

It's only fitting that the day after I finally finish a post about short films, that I stumble upon another one that has caught my eye.  It's pretty short, but very nerdy. 

"Pixels"

Wednesday, April 7, 2010

Short Films


I stumbled upon these short films about a month ago, and true to my nature, I started a blog post about it and waited a month to actually finish writing it.



Watch the film (it's only 7:32 min long) and behold the ugliness of human nature.  Warning!  Film may cause desire to connect a vacuum cleaner hose to one's own face.


One word:  EPIC.  There's a reason why it won the Academy Award for best animated short film.  It's 17 mins, but it's worth it. Check out all the different logos used in the film.  Warning! Film contains NSFW language and animated violence.


Probably the most depressing of the three.  18 mins.  Afterwards you'll be much more appreciative of what you've got.  Warning! Film may cause desire for a full rubber attire.

Tuesday, March 23, 2010

What I say [What I think]

I need [want] to blog more.  
So [Not] much to say, so little [much] time to write.  
Uninspired [lazy]. 

Monday, March 1, 2010

RTS

With the release of Starcraft 2 this year (This year? Heh, I'll keep my fingers crossed...but you never really know with Blizzard), I figured that I should brush up on my RTS skills since they're a bit rusty.  It's been a long time since I've really been into RTS games; I've mainly been sticking to my FPS (killing terrorists, zombies, and the likes).  But gaming is kinda like riding a bike, the skills are always there once you learn them, you just need to get back on the horse...or bike, whatever the metaphor is.


For those of you who aren't familiar with gaming terminology, RTS stands for real time strategy.  Examples include SC, WC, C&C, CoH, AoE, etc (n3rd props if you know what those games are).  For me however, RTS stands for real time suckage.  I learned tonight just how bad I am at these types of games.  My skills were never that great to begin with, and with so much time spent nowadays on FPS, I guess my abilities have atrophied into uselessness.  In an FPS, it's fairly simple, focus on one enemy at a time, shoot, kill, repeat.  There are elements of strategy: stealth, traps, teamwork etc, but most of the time, your attention is focused at a single target or area.  And I excel at this.  It's weird how I can multitask without problems IRL, but completely suck at it in game.  Especially when it comes to playing the Supreme Commander series.


Supreme Commander, its expansion pack - Forged Alliance, and the soon to be released sequel, Supreme Commander 2, are the most intense RTS games I've ever played.  The sheer scale of the game is massive - micro in on a single unit or macro out to see a global view, with individual units turning into shapes and symbols on a map.  It may not be the prettiest RTS graphically, but with land, air, and sea units, fully upgradable tech trees, and sometimes OP AI, it's definitely one of the most demanding.  Which is why I fail miserably at it.  It's hard enough managing my own resources in the real world, how can I expect to micro and macro manage enough resources to complete my objectives in a game?  Tonight I spent an hour building up enough defense and offense to complete the first objective, another hour to complete the second objective, only to have my base raped once I was given a third objective (the map expanded and what I thought was a well protected base - with map edges on two sides - turned into a shoddy fortification with critical flanks exposed and vulnerable to counterattack).  Two hours of strategy and planning - derailed in less than 10 minutes.  I guess I'm not cut out to be a supreme commander.  Give me a gun, some ammo, and a couple of frags any day.  


I hope they have head shots in Starcraft 2.  

Thursday, February 18, 2010

L.A.R.P.

Live Avatar Role Playing.  It just fit too well with my previous post to pass up.