Wednesday, October 14, 2009

Windows 7, Snow Leopard, the Universe, and Everything

People are crazy. I just read through the comments on someones plug for Windows 7, and as always, bitter debate ensued. There were basically two camps: Windows users and Mac users. Each group consisted of mostly common users--people who use their computers for typing up reports, sending emails, or surfing the net (side note: since the internet is a series of connected tubes, I propose we call it the "inter-tubes"). Sprinkled throughout the mud-flinging were a few IT techs and network administrators who attempted (to no avail) to even the playing field one way or the other.

Windows 7 has been hailed as the end-all be-all of operating systems by end users who just suffered through Vista. In comparison, I'm sure it's breathtaking. It hasn't been out long enough for users to find the little annoyances and fatal system bugs that will inevitably arise. Already, Windows has released numerous fixes to patch up cracks in the media and security holes. In time, W7 users will descend from their high and they'll start complaining again--this is the nature of new toys. I'm not saying they'll be as unhappy as they were with Vista; I find that extremely hard to envision. Windows users will still be Windows users because that's what they're used to.

Snow Leopard has been the hottest news in the Apple community since it came out in August 2009, but Apple seems to be slipping from their white tower. Mac users often boast that Apple computers can't get viruses and don't crash. Ever. McAfee (anti-virus software giant) recently extended support for Macs (stupid move if they can't get viruses), and Snow Leopard, even without a virus, will delete everything you ever saved if you log in as a guest. My point should be made by now. No operating system is perfect--patches and upgrades are necessary. In the end though, Mac users will be Mac users, those bumper stickers are super-glued on.

Apple advertising is shameful. Mud-flinging has always been seen for what it is, and I personally sympathize with the PC guy--if only for the fact that he's made fun of time and time again. Microsoft did a great job with the counter campaign: "I'm a PC." They're not flinging mud back; they're just making Apple look like they don't like people.

The ironic thing: PC means Personal Computers. Apple computers are PCs. The least they could do is say "Microsoft" when they mean it, but that would give them away.

Now that I've sufficiently angered both sides, allow me to stereotype Windows and Mac users. If you don't fall into my stereotypes, you don't need to be offended, just sit back and chuckle a little as you think of people you know in either boat.

Windows users are the everyday computer users. Most haven't branched out to other operating systems, and if they have, they realized that the largest support base was back where they started. They don't want the job to get their hands dirty, they just want to get the job done. Windows is everywhere: schools, businesses, internet cafes, and coffee shops.

The large majority of Mac users I've met would kill for their Mac. The article I read that inspired me to write this called them "Mac fanboys," which is a good description. These are the fanatic Mac users who will comment mean things about me when I post this message. They have a great operating system. They have white Apple stickers on their car and warn people to stay away from their precious white machines. Their paranoia is justified. Don't hate or ostracize them, they're just in the minority--and know it.

If you're a Windows user, find a Mac user who's not overly protective of his machine and give it a try. You might be surprised.

If you're a Mac user, try out Windows, it's everywhere.

Both of you, find some nerd with Ubuntu and give it a whirl. You might be surprised.

Linux people are generally nerds, but it is true that Ubuntu is becoming very user friendly. The upside is that it's free and new full versions come out twice a year. Free. Linux people don't mind searching forums for the program they need to get the job done because there are enough nerds out there to make good programs and to test one another's programs. They're the outcasts, and they don't mind.

There will always be issues to resolve no matter what operating system you use, so before you get too old, try a new one. Don't just sit down, feel uncomfortable, and leave; ask someone to introduce their world to you. They might look at you like you've lost your mind, but hey, people are crazy.

Sunday, September 20, 2009

A Poem

I wrote this poem to my wife while we were still dating. I think I wrote it down during some class that I found especially droll, and I gave it to her shortly thereafter. Today my wife returned home from a trip to her parent's house, and she brought this poem with her.

A Poem
by Robert Whiting (3/25/08)

Well I thought I'd write a poem
in a sentimental way
for your lasting entertainment
at the ending of the... hour.

If it rhymed, it'd be romantic
and it may just make you red,
so I'll modify these lyrics--
it won't sound nice when it's... spoken.

In a poem what's required
but an image or a rhyme?
If you liked it then most likely
I would sing it all the... day.

And I thought I'd write your kindness
into something sweet and true,
but my brain is far too scattered
to write imagery of... Becca.

I think this poem's finished
as your class comes to an end
soon I'll give you all this writing
and this poem you can... repair.

Friday, September 18, 2009

Return to the Code

I always figured that my last semester in college would be packed so full of classes and last minute giant assignments that I wouldn't have time to write a blog entry, let alone have extra-curricular activities.

So far, this semester is looking rather promising. Numerical analysis has complex topics, but they're manageable and interesting. Romans is intriguing yet predictable. World literature is a good introduction into what I might read after I graduate and have time to enjoy some classics, but for the time being, it is bearable.

Software engineering will actually get me somewhere in my career. We've already covered the basics of software design and testing--something I should have learned years ago. The midterm is in a week, and then the whole class will be working together on a grand project as a single company. In networks I'm learning how to watch networks and understand the underlying protocols. Soon, I'll be helping a nonprofit organization restructure their local network with the help of some other computer science majors (an opportunity never before granted).

After four years of ACM members prodding me to join, I finally joined. They showed me how to use Pov-Ray, and today they're doing a demonstration on swarm robotics. Ever since I tried competitive programming, my professors have been asking me each semester to join, and yesterday, I joined. My newly formed team finished two of the programs and successfully submitted one before the time was out. Why did I wait so long to actually get involved?

Work. Homework. Studies. How is it that college could get in the way of my learning so quickly that I missed out on the real learning? Class work provides the tools, but clubs and student organizations provide the hands on experience that make college worth it. Ironic that I pay the college so much and the clubs so little.

I have warned myself before, and I say it again, "do not allow school to get in the way of learning."

Friday, September 4, 2009

The Written Word

Throughout my life I've suffered at the hands of the English language. It may not be apparent in my final drafts, but translating the known word (ideas and concepts) into the spoken word of English (in the American dialect) and then into the written word can be a very frustrating process.

I can only assume that I am not alone in my thought process and frustrations therein. These frustrations rarely come to the surface in conversation because in this country we so frequently go through the grievous process.

I was blessed to grow up bilingual, and it is to my shame that I am no longer bilingual. In the language I grew up around, the known word still had to be translated to the spoken word, but the written word closely mirrored the spoken word. My parents sought to aid me in my frustrations by providing "The Phonics Game" to my tools of syntactic analysis, but there were so many exceptions and foreign words that had been left with their original spellings that the game only applied to an arbitrary half of the language that I needed to master.

I've known all my life that there must be some solution to this problem, and I thought, for most of my life, that it was beyond the bounds of the English language. It wasn't until I began to play with programming languages in my early years of college that I realized that the English language could be adapted to become an easily learned international language. I wasn't the only one to think of it either: Orson Scott Card referenced a language called Common in his Ender's Game series. Common, according to Card, is the "more or less phonetically spelled English language" used as a standard for international communication.

I believe it is possible to create such a standard and blend it into the school systems as the international language. With English as a phonetic language as well as the language of programming, science, and trade, other countries would more quickly accept it as the global trade language.

The English language has the most potential for such a shift (thanks to computer keyboards, no pun intended), but if the English speaking community does not make a move within the decade, Mandarin and Spanish will become the international languages. Mandarin because it is already spoken by over a billion people on the planet as a primary language, and Spanish because it is next in line behind English and quickly spreading throughout North America.

Saturday, August 8, 2009

Planting and Watching

Narrative and insight

The dogs rudely escorted me outside this morning as part of their early morning routine, but it was too late, the towel in the kennel was already damp. It was nice to be outside though. The sun was just over the horizon, the birds still sung in desperate attempt to drown out the sound of the lawnmower my neighbor methodically pushed across his lawn.

I walked over to the front step and sat. I marveled at my plants. A week ago, I had completely given up on growing flowers there when I had pulled the sun-crisped sprouts from the ground. In their place I planted Green Pepper, Squash, Tomato, and Green Onion. The Squash and Tomato patches were teaming with little life, but leaves and bud above the rest stood a Morning Glory stock. The Green Pepper and Onion patches had no signs of life.

At first, I felt rather helpless. Nothing I could do would bring them to life if they have life; digging in the soil would only harm them if they did have life. After my initial feelings of helplessness had passed, I realized the error of those emotions. My task is to plant, water, and pull weeds where needed. I did that. My task is complete. I am not the judge of who sprouts and overtakes the others or who will climb the lattice or who will spread and provide fruit or nourishment for the others. I may never see the sprouts come out of the ground or the fruit ripen. My task is simply to plant as many seeds as I can, water the ground where it is parched, and wait for the One who has control to do His work.

Maybe He will even let me watch.

Tuesday, August 4, 2009

Extended Weekend for Extended Family

Narrative: Family ties and visits.

In-laws are still rather new and enjoyable to me (they also happen to be a large majority of the followers to my blog, hello in-laws). Feel free to insert your own variety of snide joke about in-laws and outlaws here. Mine visited over the weekend, and I learned a good deal from them.

My wife's sister, her husband, and two kids drove the better half of the day to spend the weekend with Becca and I. They arrived Friday after I got off work, and we all sat around our little folding card table for some wonderful soup. James (the 7 year old) quickly identified my xbox and strategically noted that he was proficient in many gaming systems, including my xbox. I hadn't realized until then how violent my games are, only the free arcade games that came with the xbox were age appropriate. I don't value games based solely on the volume of violence and bloodshed, do I? Game creators really don't make many challenging, strategic, interesting, story-based games in the 6+ category. He seemed happy to play Pinata-Land, but he did suggest that I purchase more age appropriate games by the time they return.

The two year old was interesting to watch over the weekend. I found myself constantly paranoid that he was hiding in some dark corner of my house pooping, but that really wasn't a justified fear at all. He had on a diaper. My puppy, Daisy, has no such restraint. His language was perticuarly interesting to me. How could so few words have so many meanings? In our last encounter, my name was distinguished from the other two-syllable words: "Ba-Bo." I have no idea how this was distilled from Robert unless you follow the mental thread that justifies squinting at my name and reading it while holding your nose with one hand and your tongue with the other.

James said that because he is Peter's older brother, he is the authority on Peter's language. He told me that "Ba-Bo" means "Better." I guess that makes me a good uncle by default.

We went to a free mini-carnival at a nearby park, and I threw the frisbee for Echo while the kids played on inflatable buildings and allowed clowns to paint their faces. James and I took apart a remote control car and put it back together (and I did my best to explain basic digital electronics to him in the short spans of attention he graciously lent me).

All good things must come to a close though, and they left Sunday afternoon after we built a fort in the living room with all available blankets in the house. Becca's dad called about then and asked if he could swing by and and spend the night, so my parents-in-law drove several hours to bring us a wooden table and that old TV with the vertical collapse problem.

It's been a good weekend, but I'm still exhausted. All that cleaning before hand. All that fun during. All those failed attempts to fix my TV with vertical collapse. It's time for bed. Goodnight.

Friday, July 24, 2009

How to Fix Vertical Collapse for Large Old TVs

Warning: The opinions expressed in this blog are purely speculative. I will take absolutely no responsibility for anyone's injury or death should they attempt to recreate the instructions in this post. Opening a television or monitor can be fatal. Televisions carry extremely high voltage even after they have been unplugged for a decade or two. Extremely high voltage is not good for the human body in large doses (and "extremely high" greatly exceeds "large"). If you do not understand this warning stop reading this blog for your own sake!

First, let me explain what Vertical Collapse looks like. The best example is when you turn off your television set and the screen momentarily turns into a horizontal green line; Vertical Collapse is when it always looks like that green line. Most TVs will have an intermediate stage in Vertical Collapse before reaching such a severe case. That looks more like your television got lazy and only wanted to show two inches vertically and the full width horizontally. Most people view this as a problem because it makes it extremely difficult to see the channel number in the upper right corner (not to mention how difficult it is to see facial expressions on lines).

If your television set is experiencing Vertical Collapse, it is most likely time to get a new television. You may be rolling your eyes right now saying to yourself, "If there's a way to fix it, why buy a new one?" Well, you could die. Then where would you be? First, try whacking the top or side. If this works, put something heavy on top of the TV or up against the side and skip to the "Problem solved" part of the post.

Should you be unlucky enough to still be reading this how-to guide, take heart there might be a glimmer of almost hope. Take it to the garage, or somewhere else dusty, humid, and boiling hot. Roll it screen down on a square of carpet or something else that can cause equal static charge. Unscrew all visible screws, and remove the back cover. Do not touch anything in contact with the back middle part of the TV. Take a picture of yourself with the exposed television back and place your camera or cellphone four feet from the work area. This picture will be an excellent shot of you near victory, and if not, it will help the paramedics determine cause of death.

Roll the television set upright and plug it in. Set up a mirror so that you can see the front of the set from behind it. This step is important and can be learned in the Optics section of Physics 2, if you are incapable of performing this task, unplug the TV, put the case back on, and go buy a new one. Gently tap different sections of the main circuit board with a non-conductive material, your wife's cooking spoon will work nicely. With each tap, check the screen with the mirror; you are looking for "Vertical No-Collapse" also known as "Nertical Normalcy." If you cover the whole circuit board with no success, something more serious is wrong, and it will be cheaper to buy a new television.

For those of you still with me, congratulations. You have located the affected area on the circuit board. Unplug and roll forward your large backless television and gently maneuver the main board so that you can see the side with all the solder points. Carefully melt each solder point in position within a two inch radius of the affected area. Old television sets have a tendency to loosen their grip on some of the solder points, you just gave it new life. Set the TV up and power it on to confirm your success. Don't forget to secure the circuit board and put the case back on.

If the problem isn't solved but you know where the affected area is, you could always whack it whenever you experience Recurring Vertical Collapse Syndrome.

Problem solved.

Monday, July 13, 2009

Unfortunate Life of a Puppy

Moving will always be a stressful time, especially if you were to move permanently and into a stranger's home. The newest member of our family has had an exceptionally difficult one.

Becca and I adopted a little white and brown puppy from the local humane society on Tuesday to grow up with my one and a half year old puppy, Echo. Daisy and Echo hit it off wonderfully. He would attempt to start a game of tug-of-war and pull her across the room, and she would get up and lick his chin in adoration.

I expected that she would get sick early on from the change of diet and location, but I didn't quite expect worms in her vomit. That night my wife and I went to Walmart for some de-wormer, and later, both dogs ate that wonderful pill. Even later, they both expelled the worms from their bodies, and in the morning, I had the privilege of cleaning, bathing, and sterilizing the kennel and the dogs. They both looked rather miserable for a few days.

The plan was to take Daisy to the vet for her first round of shots, but before we could make our way to our local shot clinic, a wasp decided to do it's own vaccinating. I saw the whole thing unfold like a scene from a bad cartoon: the wasp saw the puppy, the puppy saw the wasp, the owner tried to react, the puppy decided to play with the wasp, and the wasp didn't want to play. I mashed the wasp but seconds too late. Her paw swelled up like a water balloon, and she hobbled to the kennel crying at the top of her lungs. I happened to have some children's strength diphenhydramine and measuring syringe formerly used to keep Echo drowsy on a long drive (16 hours?). My wife covered her paw with a baking powder paste, and by bedtime, she was as happy as such an unfortunate puppy could be.

On Sunday, I thought that surely this was the most unfortunate of puppies. In less than a week, she went through moving, worms medication, potty training (still very incomplete), finding her place at the bottom of the pack, and a wasp sting.

At work today, I received an unrecognized call and did not answer. When my phone informed me of the voice mail, I became interested and called voice mail. My neighbor's voice was saying something about his car and a vet and how very sorry he was. I drove to the veterinary clinic in the voice mail and found my neighbor and poor Daisy. She was breathing hard but breathing. She somehow had escaped the fenced back yard and lodged herself under his car. My neighbor was so filled with remorse that I let him go to work, and I stayed to get my little puppy x-rayed. She has some internal bruising, but no major broken bones. Her diaphragm is intact, and she can walk with a limp. All we can do now is wait and hope for the best. The pain medications will help, and so will the antibiotics.

What a most unfortunate dog.

Now I need to tell my wife...

Monday, June 29, 2009

Wedding Bells and Frizbees

The weekend was rather eventful, but I think I'll start off with some Good Idea / Bad Idea.

Good Idea: in your spare time, install a fire extinguisher in the kitchen to show your protection over your wife.
Bad Idea: test out the fire extinguisher in the kitchen.

Good Idea: wear shorts in the summer time because it is hot and humid in Texas.
Bad Idea: wear shorts to work, where they over-compensate for the hot weather.

Good Idea: kill the giant cockroach before your wife gets home.
Bad Idea: misplace an insect leg on the kitchen floor.

Good Idea: drink lots of water when you're sick.
Bad Idea: stand up quickly when nauseated and full of water.

Good Idea: get the leaky fuel line fixed on the car so that it doesn't catch on fire.
Bad Idea: fill the car with fuel before the mechanic cuts the fuel line.

Good Idea: put the dog in the back yard so he can stretch his legs while you're at work.
Bad Idea: put the dog in the back yard so he can get drenched with heavy summer rains.

All I can say is, it's been an exciting day. Although it's not completely chronological, the Good Idea / Bad Idea pretty much sums up my day. I'll allow your imagination to fill in the details. . . . Finished? Good. It all ended well, I'm sitting on my bed with my wife writing this blog instead of mourning the today that could have been; that's something right?

The better story took place before all the confusion that the flu trails in its wake. Friday morning, Becca and I drove four hours to Temple (no, we did not join a cult or go on pilgrimage). A friend from High School had asked Becca to be one of her bridesmaids, and we came when beckoned. After a few failed attempts to help, I made great headway on my most recent book Xenocide, by Orson Scott Card. I also had a great time with Becca's cousins, who we stayed with for the two nights we were in Temple. His dogs enjoyed chasing frisbees, and Echo (my dog) soon caught onto the concept of chasing after the flat and hovering tennis ball.

We stopped in Tyler on the way back, and I purchased a special ordered chefs apron (one of the last eight to be made) so that I can cook with style. Becca and I found a movie that never made it anywhere and tried to watch it over dinner. The movie was so poorly made and so incredibly predictable that we shut it off and went to bed early. Six o'clock comes around pretty fast.

Thursday, June 25, 2009

Another Day Another App

Let me explain how this whole blog thing will work itself out. I write in a variety of styles, and this is not the first blog that I've had the pleasure of writing. I'll try to give you a heads up about the category or topics covered in the entry. The categories will range from Inspirations to Instructions to Narratives to Coding Tips. This one is a narrative.

The alarm went off at 5:30 this morning; a pleasant song filled the room and quickly tore me from my dreams and placed me in Texas. I don't often get up at 5:30, and today was no exception. After a snooze my wife got up to get ready for work, and after another, I rolled out of bed to make us both breakfast. I really enjoy breakfast.

After my wife drove off to work, I read, cleaned up the kitchen, packed a lunch, and went to work. As usual, I was the first to arrive, and before anyone else had arrived, I had a cup of hot coffee in my hand and a list of completed task. I spent the rest of the day developing a new administrative panel for my dynamic webpage management system (when I say "my" I'm referring to my company, not just myself).

On the way home, I stopped at the grocery store to pick up a few of the basics: milk, eggs, bread, corn starch, and cotton rounds. I've noticed that my grocery lists have already begun the obvious shift from a bachelor list to a married man list; the recent development is quite enjoyable to observe (and participate in). I would have been out of the store within ten minutes, but by the time I had checked off all the other items on my list, I discovered that I hadn't the fainted clue what corn starch looks like. I imagined a clear liquid in a medium glass bottle with a picture of corn on it. Half an hour later, I asked someone who worked there what corn starch looked like, and she immediately walked me to the baking section next to the flower and picked up a can with big letters across the front: Corn Starch. Incidentally, the first place I looked was in the Baking/Flour department.

I arrived home to see my beautiful wife cooking dinner and my energetic dog running laps around the island. After a long day, it was good to be home.