Marvel's Star Wars #1 is the Balls

Welcome home, Star Wars. After nearly twenty-five years at Dark Horse Comics, the Star Wars franchise is back at home in the hands of Marvel Comics, the company that first published comic books set in that far-away galaxy. 

When it was announced that Marvel would be regaining the rights from Dark Horse, and that Disney/LucasFilm/Marvel would be essentially "rebooting" (I'm not a fan of that word, btw) the universe, I was both apprehensive yet relieved. In one sense, it was hard for me to think that a lot of the things I, as a Star Wars fan, have grown to love about the Expanded Universe -- the incredibly excellent Thrawn Trilogy by Timothy Zahn comes to mind -- are no longer considered canon. However, the storyline has become so convoluted, so long, that a reboot may just be what the franchise, specifically the Expanded Universe (ie, comic book, novel and video game properties), needs to -- oh god, I hate to say it...don't make me say it...bring balance to the Force.

So here we are with the first of the new series under new ownership. Written by Marvel writer Jason Aaron, who also scripted the mind-shattering summer event Original Sin, Star Wars #1 is already the biggest-selling comic of 2015. In fact, the reboot under the Marvel banner saw solicitation sales come in over a million units, with a ton of variant covers (I'm hoping to score a sketch cover myself). 

If you have't read it yet, feel free to stop here. Spoilers are contained within. If you don't care, or know you're not going to read it, continue on ahead.

Reading it made me feel like a little kid again. Instead of setting the comic in a time period with characters we may not know, Marvel puts us right in the middle of things with Han, Luke, Leia, Chewie and the droids. Set in between A New Hope and Empire Strikes Back may mean we won't see anything too dramatic (Luke won't get a leg chopped off; Han won't die, etc), but drama and tension are both very present.

The book starts with the classic crawl -- which had me humming the theme music in my head -- and the likenesses of the actors as our main characters take us right into an awesome sabotage story. There are a couple of splash pages in here too that took my breath away. The art is superb, and I am waiting impatiently for Issue 2.

That's not to say it's without error, however. I'd give the issue a solid 9, but a few minor things keep it from being a 10. Leia is a bit too brash here. Yes, we want a strong female character, and we know that the princess of Alderaan is no damsel in distress, but she makes a decision in the book that makes me scratch my head a little.

All in all though, it's a tour-de-force (hehehe, get it?) and any reservations I may have had are completely out the window. Welcome home, Star Wars. It's been a long time coming. 

Back to the Future in 2015

Back to the Future is the first movie I vividly remember watching. I was probably four years old. I wasn't going to bed when I was supposed to, so my parents let me stay up late with them and watch this movie they had rented on video.

Even at four years old, this movie had a huge impact on me. The skateboarding scenes, the flames, the DeLorean ("You made a time machine?! Out of a DeLorean?!"). Michael J. Fox was my first movie star hero. I didn't discover Star Wars until I was about ten, so I spent several years pretending I was Marty McFly. 

(Side note: the first "bad word" I remember saying in front of my dad -- we were playing with my remote control car. I turned to look at him and said, "When this baby hits 88, you're going to see some serious shit!")

So, a few nights ago, my seven year-old son wasn't going to bed and wasn't tired. It was 11pm, and browsing through our movies, I asked him, "Have you seen Back to the Future?"

"No," he said. So I put it on, and we watched it together. 

The good news is, the movie still holds up. It perfectly encapsulates that high school trying-to-be-something-even-though-some-people-say-I-won't-amount-to-anything feeling. The awkwardness of Marty and his mom and his dad in 1955 is still hilarious, and yes -- still creepy. 

It was great watching my son watch my favorite movie of my childhood. He was fascinated with the DeLorean. He thought Doc Brown was crazy. He thought Marty McFly was the flyest guitar player this side of Huey Lewis. 

And just like me, nearly 25 years ago, the ending-- where Doc says "Roads? Where we're going we don't need roads," and the time machine mother-loving FLIES -- absolutely floored him. 

"It can fly?!"

Guess we need to watch Part II now.

Nerd Food: Mountain Dew Cake

Very possibly our Dungeon Master.

It's no secret: nerds love Mountain Dew. It's pretty much the Official Drink of D&D players all over the world. When I was a teenager, a 12-pack of the glorious, neon yellow super-sugared soda was pretty much a staple (along with a giant bag of Fritos and/or Doritos) when we were playing our Dungeons & Dragons campaigns.

So, if you're a nerd, it's pretty much a given that you've got a few cans of the "nectar of the gods" in your fridge. Today, I'm going to show you how, with a few other ingredients, to turn that soda into a delicious MOUNTAIN DEW CAKE that you can take to your next adventure session (or, eat all yourself within the comfort and privacy of your own home -- no judgement here, bro).

First, you'll need to gather the necessary items.

For the cake itself, you'll need:

Some of the stuff you'll need.

• One box of Duncan Hines Lemon Supreme Cake
• 1 (3.4 ounce) box Lemon Jell-O Instant Pudding Mix (you can go generic store brand here.)
• 4 large eggs
• 1/2 cup vegetable oil
• 1 12oz can of Mountain Dew (equals to 1 1/2 cups)
• Large (10-cup) Bundt cake pan
• Nonstick spray
• Flour

And for the glaze:

• 1/2 cup (1 stick) UNSALTED butter. (Go with real butter here. Margarine just doesn't do it.
• 1 cup Sugar
• 1/2 cup Mountain Dew

First things first, preheat your oven to 325 degrees. Then spray the inside of your cake pan with the nonstick spray. Sprinkle in a little flour and get a good thin coating of flour in there. That'll keep the cake from sticking from the pan. 

Take your cake mix and Jell-O pudding mix and throw that shiz in a big mixing bowl. Add the eggs and oil and blend it on medium with your mixer while slowly adding in the full can of Mountain Dew.

Once all that is all mixed and you've got a nice batter, pour it into your Bundt pan. Throw it in the oven and set a timer for 45 minutes. Go play some video games/browse 9gag/catch up on Joshua Williamson's Nailbiter (Vol 1 available on Amazon). Once your timer goes off, or you magically remember that 45 minutes have passed, take your cake out of the oven and let it cool in the pan for about 5 minutes. After 5 minutes, transfer it onto a wire rack to cool.

While the cake is cooling, you need to make the glaze. In a medium saucepan, melt 1/2 cup (1 stick) butter. Once it's melted add the 1 cup sugar and 1/2 cup Mountain Dew (you'll have a little more than half a can of Mountain Dew left. Drink it.) Melt all that together and stir with a wooden spoon until all the sugar is dissolved. Take it off the heat and let the glaze cool for about 10-15 minutes. 

Poke holes in the top of your cake with a skewer, then slowly pour the glaze over, consistently covering it. Then let it cool completely, which will take about 30 minutes. 

There you go! You've got yourself a Mountain Dew cake!

Completed cake.

Trick-or-treating Strategy for Winners

WARNING: Non-computer post.

Because nerdiness pays the bills, except when it doesn't.

Halloween is Friday! I love Halloween. I'm still a kid at heart, and love the dress-up, the jack-o-lanterns; all the pomp and circumstance is so much fun. Plus, it's the only holiday where I can put on a Spider-man costume and run around the neighborhood without having the cops called on me.

My kids are the perfect age for trick-or-treating. They look adorable in costumes, yet are old enough to carry their own loot bags and walk at a normal-sized human pace. Also, no strollers is a big deal. So, at seven and nine years old, we have a perfect trick-or-treating strategy for optimal candy-per-child ratio. 

1. Be very cute, very creative, or very scary – The costume is the biggest part. And don't just slap on some face paint and a black sweater and call it a day. Candy-givers *do* play favoritism, and if you're the cutest, most creative, or most scary, they're more likely to hand you an extra piece of candy. I know this, because I've done the research.

2. Go retro – This goes hand-in-hand with the previous point. The people who are handing out candy are my age or older. So, if you dress as something that appeals to them (ALF, Strawberry Shortcake, Rainbow Dash from My Little Pony, etc), you'll activate that nostalgic part of their brain that'll make them want to give you more candy. It's all psychological at that point.

3. Leave the cute plastic pumpkin bucket at home – Plastic pumpkin will hold approximately 16 oz of candy at the most. It's a pain to constantly dump that thing out. Grab your best pillowcase or reusable shopping bag for optimal candy-hoarding.

COROLLARY: If you're using your vehicle as "home base" between blocks, take the plastic pumpkin and dump it into a sack between blocks. This will make people think you don't have a lot of candy when you show up to their front door with a half-filled pumpkin. They'll take pity on you and give you more candy than normal. 

4. Map out your trick-or-treating – Logistics is important, folks. If it had not been for logistics, America may not have won the Civil War. And that's a fact. Also, Google Maps is a thing. Use that to map out your route. If you live in cookie-cutter square blocks, it's easiest to zig-zag by walking up one side, down the other, and go on to the next block, hitting the houses on the side streets. 

5. Wear sneakers – Sure, you may be tempted to wear the heels or pirate boots to complete your costume, but sneakers are your best bet for moving fast.

6. Hem, hem, hem – You may look frightful in that grim reaper costume, but if the rope is dragging near your feet, it'll slow you down. Hem that sucker up. You'll be happy when you don't trip on the sidewalk.

7. Don’t go out too early – If you’re one of the first kids out in the neighborhood, homeowners will be rationing out the candy, only giving you one Tootsie Roll to make sure there’s enough for later trick-or-treaters. 6:00-6:30pm is the optimal starting time. 

8. Ignore the houses with no lights or disappointed children – Lights out means they’re not home or don’t want to be bothered. Others may leave the light on, but won’t answer the door. Most of these houses are void of Halloween decorations. You can usually tell there’s a dud house when the group of trick-or-treaters before you leaves mumbling.

9. The more decorated the house, the better the candy – Some folks absolutely love Halloween. Scout out your neighborhood a few days before the night of and mentally note the ones that have a lot of decorations up. They'll be your best bet for the most candy-per-house. 

12. Be patient – Don’t be so quick to run to the front of the group and be the first to say “Trick or treat!” If you’re the last person in the group, sometimes the candy giver will slip you an extra piece of candy or two for being patient.

13. Stay in 2's – Stay in packs of two. Why? Because a whole herd of kids will invariably kick in the "one for you, one for you" rationing mentality of the candy-giver. Stay in packs of two so you don't overload them. They'll be more likely to give you a few pieces per handout. Again, science!

14. Don’t forget your immediate neighbors – They love seeing the neighborhood kids they know (unless you give them a reason not to like you), and will give you more candy.

15. Don’t trick-or-treat too late – If you’re knocking on someone’s door at 11 pm, they’re bound to be angry. No candy for you. Start winding down between 8:30 and 9:00. This is usually when people start giving out handfuls of candy, since they don’t want the calorie-laden temptations in their houses on November 1.

And lastly...

16. Remember to say thank you!

Here is the crappy candy list. Don't hand this stuff out, folks. It's not good for the environment.

– Apples
– Pencils
– Toothbrushes
– Sticky candies that get caught in your teeth (some are great, some are meh, like Dots, some are flat-out miserable)
– Candy corn. Don’t get me wrong, I love ‘em, but something is just weak about handing out factory-sealed plastic baggies of them. Leave them in the office treat bowl. If you’re giving out tiny candies, try Nerds or Reese’s Pieces. Not these sugary sweets that just end up making your sugar hangover 10 times worse.
– A single caramel cube. CARAMEL CUBES MUST BE JUST AN ADDON TO ANOTHER CARAMEL CUBE OR CANDY. If you give me just one, I’ll take it because they’re ridiculously tasty. But you’re going to wake up and there’ll be a tiny gourd missing from your porch, and an electric tea candle from your flashy pumpkin lawn display.
– Raisins. RAISINS?! 

Micosoft Surface Pro Review

I had a 2011 iMac that we didn't use. It was large, immobile and didn't fit what I needed in a computer. Though fast -- and let's face it, it's hard to beat a Mac when it comes to hardware -- it just didn't fit my ever-increasing mobile life. My main laptop was a CR-48 Google prototype Chromebook that I flashed to run Ubuntu 12.04.

So, I got rid of the iMac and bought a Microsoft Surface Pro. After 5 days of use, this is my review.


I hated Windows 8. It made no sense to me. The whole Metro start screen, the bipolar desktop thing, the side-menus. All of it was the most extreme example of compromise I've ever seen in OS form. But that was only using it on a desktop/laptop interface without a touchscreen. Then I got it with the Surface. Microsoft did a horrible job at marketing Windows 8, and they did an even worse job of making it make sense on non-touch devices. However, on the touch interface, you realize it makes perfect sense. A desktop or non-touch laptop doesn't have a capacitive Windows home button on the hardware. I came to realize very quickly that the Surface was built for Windows 8 and Windows 8 was built for Surface.

Surface Pro is different than most tablets, though. With an i5 processor and its 4GB of RAM and giant 128GB SSD, its more ultrabook than tablet. It's also heavier than most tablets, at around two pounds with the Type Cover 2. So is it a laplet? A tabbook? An Ultratablet? I don't know. Perhaps it truly is in a category by itself. But make no mistake, it is in a class by its own and it's an elite class indeed.

For starters, the display is a full 1080p HD screen and (at least in my opinion) puts the Apple's Retina display to shame. Netflix, Kindle and even YouTube look amazing. The widescreen allows the biggest benefit of Windows 8 over the standard tablet interface -- multiple apps open at once. It's awesome to have Amazon open on one side, surfing through some cool products I'd like, and having Netflix open on the other half, running through episodes of LOST or something. Like right now. I'm typing this with Chrome opened up on the left-hand side of my screen, and watching Netflix on the other side.

And with this being the Pro version of the Surface tablet, and not the RT, this is full Windows 8. Want to run Quickbooks on this? You got it. Want Opera web browser? Check. Want to run Chrome in Windows 8 metro mode that opens a full screen Chrome OS-style window? Check again. Side benefit: apps that require a premium subscription for mobile access (such as Spotify) work just fine on here as a desktop app -- because that's exactly what it is.

The attachable keyboard cover leapfrogged the iPad and other tablets in productivity matters. To be able to sit down -- like right now! -- and bang out a blog post, or do some coding in Ruby. Out of personal experience, I have to recommend that you spend the extra $10 for the TypeCover over the TouchCover. Both are great, but nothing beats the physical keys of the TypeCover. Sure, it's a bit more bulky but worth it.

Despite these amazing benefits, it's not 100% perfect. The battery isn't great. I get about 4-5 hours on a single charge. It's not horrible, but don't expect the battery life you'd get on something with an ARM chip like an iPad or a Kindle Fire HDX. That's kind of the tradeoff you get with a full desktop-class OS and hardware here. And the app store is still a bit lethargic. No official Spotify app was glaring as well as no Amazon VOD or Cloud Player app (though, admittedly, you can download those desktop apps from the Amazon site).

All in all, I give the Surface Pro a B+. Battery life and app store still keep this from being perfect, but it's leaps and bounds better than any other tablet when it comes to "doing the most." I don't have to carry around a tablet and a laptop now. I've got both in one package, and it's quite fantastic.

In the Beginning (Ruby on Rails)

I started reading "Hatching Twitter" the other day, and learned while reading that Jack used Ruby on Rails to write the program and code the site that would become twitter. I was immediately, for some reason, completely enamored with wanting to learn this computer language. I have an idea for a tech startup that would require the kind of programming and coding that RoR provides, and I want to learn it. Plus, as part of my job, I want to have an edge on my competitors. Where they are using old-school WordPress templates and PHP coding, I want to use something that could give one of our clients a better website.

But I have to learn the language first! And there's definitely a huge difference in designing a site using something like Squarespace and actually coding it from scratch. Let's be honest, too. Computer repair and service isn't going to pay the bills forever. Eventually our business will evolve and change, and learning to code may be the best way to ensure a future for us.

So I bought a couple of Ruby on Rails books on my kindle and started a few tutorials online. But tonight, I found an actual class from University of Texas. A 10-week course on learning Ruby on Rails from a professor who was kind enough to put the entire course online for free. (btw, if you're interested in learning for yourself as well, you can find the course here. And thank you to Schneems for putting it on the web for us!)

So, my blog will be about what I learn and how far I go in the next 10 weeks in this learning process.

WHAT I NEED TO LEARN:

- Ruby language
- How Rails works
- Scaffolding
- PostgreSQL databases

 Tonight in the UT RoR course, I learned the beginning of PostgreSQL databases, and why they are important in Rails to create dynamic websites. Dynamic websites are sites that change. Think Facebook. It changes everytime you get on, and it is different for each user. Or Twitter.

Databases are read in strings, integers and boolean (true/false).

I have a lot to learn. But I'm excited. I'll keep you posted.